L'appel à conférenciers pour PostgreSQL Brazil, événement tenu du 15 au 17 août 2013 à Porto Velho, État du Rondônia au Brésil, est lancé. Les propositions sont attendues jusqu'au 15 mars : http://pgbr.postgresql.org.br/2013/chamada.en.php

Le programme du PGCon, la conférence mondiale des développeurs PostgreSQL, est en ligne : http://www.pgcon.org/2013/schedule/events.en.html?pgannounce

Les nouveautés des produits dérivés

Offres d'emplois autour de PostgreSQL en février

PostgreSQL Local

  • Le PyPgDay aura lieu le 13 mars au Santa Clara Convention Center, le premier jour de la PyCon. Informations par là : http://wiki.postgresql.org/wiki/PyPgDay2013
  • Le PGDay 2013 de New-York City aura lieu le 22 mars : http://pgday.nycpug.org/
  • Le PgDay Fr est l'événement majeur de la communauté francophone. La date limite pour les propositions de conférence est le samedi 24 mars 2013 à 23h59 CEST : http://pgday.fr/call_for_papers
  • La PostgreSQL Session est programmée pour le 28 mars 2013 à Paris. L'appel à conférenciers est lancé : http://www.postgresql-sessions.org/en/5/
  • PGCon 2013 aura lieu les 23 & 24 mai 2013 à l'Université d'Ottawa : http://www.pgcon.org/2013/
  • La 6ème conférence annuelle "Prague PostgreSQL Developers Day", organisée par le CSPUG (Groupe des utilisateurs tchèques et slovaques de PostgreSQL), aura lieu le 30 mai 2013 à la Faculté des Sciences Mathématiques & Physiques de l'Université Charles (Malostranske namesti 25, Prague). Les candidatures des conférenciers sont attendues jusqu'au 14 avril à l'adresse <info AT p2d2 POINT cz>. D'avantage d'informations sur le site : http://www.p2d2.cz/

PostgreSQL dans les média

PostgreSQL Weekly News / les nouvelles hebdomadaires vous sont offertes cette semaine par David Fetter. Traduction par l'équipe PostgreSQLFr sous licence CC BY-NC-SA.

Proposez vos articles ou annonces avant dimanche 15:00 (heure du Pacifique). Merci de les envoyer en anglais à david (a) fetter.org, en allemand à pwn (a) pgug.de, en italien à pwn (a) itpug.org et en espagnol à pwn (a) arpug.com.ar.

(lien vers l'article original)

Correctifs appliqués

Peter Eisentraut a poussé :

Alvaro Herrera a poussé :

Heikki Linnakangas a poussé :

  • Fix yet another typo in comment. Etsuro Fujita http://git.postgresql.org/pg/commitdiff/5d6899dbae7ac19d90f135e2ad64832e4ca8d064
  • Don't pass NULL to fprintf, if a bogus connection string is given to pg_dump. Back-patch to all supported branches. http://git.postgresql.org/pg/commitdiff/2930c05634bcb7491bc443a493405e927ed08443
  • Fix pg_dumpall with database names containing =. If a database name contained a '=' character, pg_dumpall failed. The problem was in the way pg_dumpall passes the database name to pg_dump on the command line. If it contained a '=' character, pg_dump would interpret it as a libpq connection string instead of a plain database name. To fix, pass the database name to pg_dump as a connection string, "dbname=foo", with the database name escaped if necessary. Back-patch to all supported branches. http://git.postgresql.org/pg/commitdiff/f435cd1d385859a0cdb1d70fccc21dde2b1ee116
  • Fix thinko in previous commit. We must still initialize minRecoveryPoint if we start straight with archive recovery, e.g when recovering from a normal base backup taken with pg_start/stop_backup. Otherwise we never consider the system consistent. http://git.postgresql.org/pg/commitdiff/6c4f6664b201bea77eb6e3f813559e3911a5ef35
  • If recovery.conf is created after "pg_ctl stop -m i", do crash recovery. If you create a base backup using an atomic filesystem snapshot, and try to perform PITR starting from that base backup, or if you just kill a master server and create recovery.conf to put it into standby mode, we don't know how far we need to recover before reaching consistency. Normally in crash recovery, we replay all the WAL present in pg_xlog, and assume that we're consistent after that. And normally in archive recovery, minRecoveryPoint, backupEndRequired, or backupEndPoint is set in the control file, indicating how far we need to replay to reach consistency. But if the server was previously up and running normally, and you kill -9 it or take an atomic filesystem snapshot, none of those fields are set in the control file. The solution is to perform crash recovery first, replaying all the WAL in pg_xlog. After that's done, we assume that the system is consistent like in normal crash recovery, and switch to archive recovery mode after that. Per report from Kyotaro HORIGUCHI. In his scenario, recovery.conf was created after "pg_ctl stop -m i". I'm not sure we need to support that exact scenario, but we should support backing up using a filesystem snapshot, which looks identical. This issue goes back to at least 9.0, where hot standby was introduced and we started to track when consistency is reached. In 9.1 and 9.2, we would open up for hot standby too early, and queries could briefly see an inconsistent state. But 9.2 made it more visible, as we started to PANIC if we see a reference to a non-existing page during recovery, if we've already reached consistency. This is a fairly big patch, so back-patch to 9.2 only, where the issue is more visible. We can consider back-patching further after this has received some more testing in 9.2 and master. http://git.postgresql.org/pg/commitdiff/abf5c5c9a4f142b3343614746bb9e99a794f8e7b

Tom Lane a poussé :

Andrew Dunstan a poussé :

Correctifs rejetés (à ce jour)

  • Pas de déception cette semaine :-)

Correctifs en attente

  • Zoltan Boszormenyi sent in a pair of patches to fix a pair of bugs: one where recovery.conf was generated without double-escaping quoted values, and another in parsing the connection string in libpq when the parameter value starts with a single-quote character.
  • Gurjeet Singh sent in a patch to make pgindent work cleanly.
  • Gurjeet Singh sent in a patch which adds a one-line comment to improve understanding of the VARSIZE_ANY_EXHDR macro.
  • Kevin Grittner sent in two revisions of a patch to add a pg_matviews catalog view.
  • Alexander Law sent in a patch to fix an issue where postmaster messages were unreadable in a Windows console.
  • Andres Freund sent in a patch to fix up the conversion of a relation to a view for TOAST, etc.
  • Amit Kapila and Heikki Linnakangas traded patches to add PQconninfoParseParams and PQconninfodefaultsMerge to libpq.
  • Etsuro Fujita sent in another revision of a patch to add hooks for pre- and post-processor executables for COPY and \copy.
  • Alvaro Herrera sent in another revision of a patch to add an event trigger on DDL DROP.
  • Michael Paquier sent in two more revisions of a patch to add REINDEX CONCURRENTLY.
  • Pavel Stehule sent in another revision of a patch to unify the serializations of booleans and domains over same in XML.
  • Dimitri Fontaine sent in another revision of a patch to add Extension Templates.
  • Zoltan Boszormenyi sent in another revision of a patch to fix a lock timeout issue.