Nouvelles hebdomadaires de PostgreSQL - 9 mai 2010

PostgreSQL 9.0 beta 1 a été publiée. À vos tests ! http://www.postgresql.org/developer/beta

Le "Prague PostgreSQL Test Day" aura lieu le 21 mai 2010 à Prague, République Tchèque : http://www.nic.cz/page/747/test-the-new-beta-version-of-postgresql-in-the-cz.nic-laboratories/

Le nouveau bureau de l'association PostgreSQLFr a été élu avec, à sa tête, le président Jean-Christophe Arnu, le vice-président Cédric Villeman, le trésorier Stéphane Schildknecht et le secrétaire Patrick Francelle. D'avantage de détails sur : http://www.postgresql.fr/asso:elections

Les nouveautés des produits dérivés

• pgfincore, 0.41, un ensemble de fonctions de gestion bas-niveau des relations, utilisant mincore pour explorer la mémoire cache : http://pgfoundry.org/projects/pgfincore/
• James W. Pye a publié une nouvelle version de PL/Python3 : http://python.projects.postgresql.org/backend/
• RHQ 3.0.0.B05, un gestionnaire système et outil de surveillance utilisant PostgreSQL : http://rhq-project.org/

La fonctionnalité 9.0 de la semaine

Vous pouvez créer des déclencheurs propres à une colonne, c'est-à-dire des déclencheurs qui ne se mettent en branle qu'à la modification de certaines colonnes. La syntaxe, comme décrite dans SQL:2008, est CREATE TRIGGER nom_du_trigger (BEFORE|AFTER) UPDATE OF col1 [,col2...coln] ON nom_de_la_table FOR EACH ROW EXECUTE PROCEDURE fonction_declenchee();

Offres d'emplois autour de PostgreSQL en Mai

• Internationales : http://archives.postgresql.org/pgsql-jobs/2010-05/threads.php;
• Francophones : http://forums.postgresql.fr/viewforum.php?id=4.

PostgreSQL Local

• La PgCon 2010 aura lieu les 20 & 21 mai 2010 à Ottawa avec des tutoriels les 18 et 19 : http://www.pgcon.org/2010/registration.php
• Les inscriptions sont ouvertes pour l'Open Source Bridge et les conférences sont annoncées ! L'événement aura lieu du 1er au 4 juin 2010 à Portland (Oregon) : http://opensourcebridge.org/events/2010/proposals/
• Michael Renner tiendra une conférence au AMOOCON qui aura lieu du 4 au 6 juin 2010 : http://www.amoocon.de/speakers/214
• La "Southeast Linuxfest 2010" aura lieu à Spartanburg (Caroline du Sud, États-Unis) les 12 & 13 juin. Participations/réunions et mécénats encore proposables : http://southeastlinuxfest.org/
• L'OSCON aura lieu à Portland (Oregon) du 19 au 23 juillet 2010 : http://www.oscon.com/oscon2010

PostgreSQL dans les média

• Planet PostgreSQL : http://planet.postgresql.org/
• Planet PostgreSQLFr : http://planete.postgresql.fr/

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

Heikki Linnakangas a commité :

• Add cross-reference from wal_level to hot_standby setting. Update the PITR documentation to mention that you need to set wal_level to 'archive' or 'hot_standby', to enable WAL archiving. Per Simon Riggs's request.
• In pgsql/doc/src/sgml/high-availability.sgml, change "literal" tag to the more appropriate "firstterm", when describing what "eventually consistent" means.
• In pgsql/doc/src/sgml/config.sgml, change wording so that you don't need to understand that wal_levels form a hierarchy. Per Simon Riggs's suggestion.
• In pgsql/src/backend/access/transam/xlog.c, need to hold ControlFileLock while updating control file. Update minRecoveryPoint in control file when replaying a parameter change record, to ensure that we don't allow hot standby on WAL generated without wal_level='hot_standby' after a standby restart.
• In pgsql/doc/src/sgml/intarray.sgml, fix incorrect parameter tag in docs, spotted by KOIZUMI Satoru.

Alvaro Herrera a commité :

• In pgsql/doc/src/sgml/mvcc.sgml, remove spurious dot, per bug #5446 reported by Koizumi Satoru.

Tom Lane a commité :

• Fix backpatching error in recent patch for ALTER USER f RESET ALL behavior. The argument list for array_set() changed in 8.2 (in connection with allowing nulls in arrays) but the newer argument list was used in the patches applied to 8.1 and 8.0 branches. The patch for 7.4 was OK though. Per compiler warnings.
• In pgsql/src/bin/psql/psqlscan.l, fix psql to not go into infinite recursion when expanding a variable that refers to itself (directly or indirectly). Instead, print a message when recursion is detected, and don't expand the repeated reference. Per bug #5448 from Francis Markham. Back-patch to 8.0. Although the issue exists in 7.4 as well, it seems impractical to fix there because of the lack of any state stack that could be used to track active expansions.
• In pgsql/src/makefiles/Makefile.linux, on Linux, use --enable-new-dtags when specifying -rpath to linker. This should allow LD_LIBRARY_PATH to work as desired. Per trouble report from Andy Colson.
• Work around a subtle portability problem in use of printf %s format. Depending on which spec you read, field widths and precisions in %s may be counted either in bytes or characters. Our code was assuming bytes, which is wrong at least for glibc's implementation, and in any case libc might have a different idea of the prevailing encoding than we do. Hence, for portable results we must avoid using anything more complex than just "%s" unless the string to be printed is known to be all-ASCII. This patch fixes the cases I could find, including the psql formatting failure reported by Hernan Gonzalez. In HEAD only, I also added comments to some places where it appears safe to continue using "%.*s".
• Adjust comments about avoiding use of printf's %.*s. My initial impression that glibc was measuring the precision in characters (which is what the Linux man page says it does) was incorrect. It does take the precision to be in bytes, but it also tries to truncate the string at a character boundary. The bottom line remains the same: it will mess up if the string is not in the encoding it expects, so we need to avoid %.*s anytime there's a significant risk of that. Previous code changes are still good, but adjust the comments to reflect this knowledge. Per research by Hernan Gonzalez.
• In pgsql/doc/src/sgml/ecpg.sgml, fix typo: PGTYPES_NUM_OVERFLOW should be PGTYPES_NUM_UNDERFLOW. Noted by KOIZUMI Satoru.
• In pgsql/src/backend/replication/walsender.c, fix missing static declaration for XLogRead().
• In pgsql/src/bin/psql/print.c, suppress signed-vs-unsigned-char warning.

ITAGAKI Takahiro a commité :

• In pgsql/src/port/chklocale.c, code page for EUC-KR is surely 51949.

Michael Meskes a commité :

• In pgsql/src/interfaces/ecpg/ecpglib/connect.c, ECPG connect routine only checked for NULL to find empty parameters, but user and password can also be "".

Correctifs rejetés (à ce jour)

• Pas de déception cette semaine :-)

Correctifs en attente

• Pavel Stehule sent in a patch to remove the limit on the number of parameters passed to xslt_process() in contrib/xml2. It had been 10.
• Simon Riggs sent in a WIP patch to change max_standby_delay to rely on WAL receipt timestamp instead of log timestamp, per suggestion from Tom Lane.
• Pavel Stehule sent in a patch to add new optional arguments to string_to_array() and array_to_string() which allow for an explicit NULL string rather than to have NULL disappear unconditionally.
• Peter Eisentraut sent in a patch to fix bug 5447, which relates to VPATH builds.
• Simon Riggs sent in a patch intended to fix the issue where Hot Standby/Streaming Replication databases have slower queries on replicas than origin.
• Pavel Stehule sent in a patch to create to_string() and to_array() functions which include NULL handling different from the current "eliminate NULLs" behavior of array_to_string() and string_to_array().
• Andy Lester and Robert Haas traded patches to clarify some CLUSTER behavior.
• Joel Jacobson and ITAGAKI Takahiro traded patches to add some new stat transaction views for 9.1.
• Nikhil Sontakke sent in two revisions of a patch intended to change the behavior of memory with set-returning functions.
• Simon Riggs sent in a patch intended to fix some behavior with Hot Standby.
• Simon Riggs sent in a patch to add a SQLSTATE for Hot Standby.
• Robert Haas sent in a patch to avert doom around temprels.