La PostgreSQL Conference Europe 2015 qui aura lieu du 27 au 30 octobre accepte à présent les inscriptions des auditeurs : http://2015.pgconf.eu/registration/

Les nouveautés des produits dérivés

Offres d'emplois autour de PostgreSQL en juin

PostgreSQL Local

  • La deuxième Conférence PostgreSQL Suisse se tiendra à Rapperswil les 25 & 26 juin 2015 : http://www.postgres-conference.ch/
  • La conférence PGDay UK aura lieu le 7 juillet 2015 - elle vise les membres de la communauté PostgreSQL anglaise. L'appel à conférenciers expire le 13 avril : http://www.postgresqlusergroup.org.uk
  • Le PGDay Campinas 2015 aura lieu à Campinas (Brésil) le 7 août. L'appel à conférenciers expire le 31 mai : http://pgdaycampinas.com.br/english/
  • L'appel à conférenciers pour le PostgresOpen 2015, programmé à Dallas (Texas) du 16 au 18 septembre, a été lancé : http://2015.postgresopen.org/callforpapers/
  • L'appel à conférenciers pour la session PostgreSQL n°7 (24 septembre 2015 à Paris) est lancé jusqu'au 15 juin 2015 : call-for-paper <AT> postgresql-sessions <DOT> org : http://www.postgresql-sessions.org/7/about
  • PostgreSQL Conference Europe 2015 aura lieu du 27 au 30 octobre au Vienna Marriott Hotel à Vienne (Autriche). L'appel à conférenciers est lancé jusqu'au 7 août : http://2015.pgconf.eu/
  • PGConf Silicon Valley 2015 se tiendra au centre de convention sud de San Francisco les 17 & 18 novembre. L'appel à conférenciers porte jusqu'au 15 juin : http://www.pgconfsv.com

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. La version originale se trouve à l'adresse suivante : http://www.postgresql.org/message-id/20150621221026.GB32298@fetter.org

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.

Correctifs appliqués

Michael Meskes pushed:

Andrew Dunstan pushed:

Noah Misch pushed:

  • Detect setlocale(LC_CTYPE, NULL) clobbering previous return values. POSIX permits setlocale() calls to invalidate any previous setlocale() return values. Commit 5f538ad004aa00cf0881f179f0cde789aad4f47e neglected to account for that. In advance of fixing that bug, switch to failing hard on affected configurations. This is a planned temporary commit to assay buildfarm-represented configurations. http://git.postgresql.org/pg/commitdiff/b76e76be460a240e99c33f6fb470dd1d5fe01a2a
  • Revert "Detect setlocale(LC_CTYPE, NULL) clobbering previous return values." This reverts commit b76e76be460a240e99c33f6fb470dd1d5fe01a2a. The buildfarm yielded no related failures. http://git.postgresql.org/pg/commitdiff/1f2a378de41bf3e516b8d2c4d65790aeefbfb89d
  • Fix failure to copy setlocale() return value. POSIX permits setlocale() calls to invalidate any previous setlocale() return values, but commit 5f538ad004aa00cf0881f179f0cde789aad4f47e neglected to account for setlocale(LC_CTYPE, NULL) doing so. The effect was to set the LC_CTYPE environment variable to an unintended value. pg_perm_setlocale() sets this variable to assist PL/Perl; without it, Perl would undo PostgreSQL's locale settings. The known-affected configurations are 32-bit, release builds using Visual Studio 2012 or Visual Studio 2013. Visual Studio 2010 is unaffected, as were all buildfarm-attested configurations. In principle, this bug could leave the wrong LC_CTYPE in effect after PL/Perl use, which could in turn facilitate problems like corrupt tsvector datums. No known platform experiences that consequence, because PL/Perl on Windows does not use this environment variable. The bug has been user-visible, as early postmaster failure, on systems with Windows ANSI code page set to CP936 for "Chinese (Simplified, PRC)" and probably on systems using other multibyte code pages. (SetEnvironmentVariable() rejects values containing character data not valid under the Windows ANSI code page.) Back-patch to 9.4, where the faulty commit first appeared. Reported by Didi Hu and æž—é¹ç¨‹. Reviewed by Tom Lane, though this fix strategy was not his first choice. http://git.postgresql.org/pg/commitdiff/f0a264a362343287051c4737b01aa3ebe36f21a6

Robert Haas pushed:

Tom Lane pushed:

  • Fix bogus range_table_mutator() logic for RangeTblEntry.tablesample. Must make a copy of the TableSampleClause node; the previous coding modified the input data structure in-place. Petr Jelinek http://git.postgresql.org/pg/commitdiff/be87143fe90adf8862791aeddd76151e88ce5603
  • In immediate shutdown, postmaster should not exit till children are gone. This adjusts commit 82233ce7ea42d6ba519aaec63008aff49da6c7af so that the postmaster does not exit until all its child processes have exited, even if the 5-second timeout elapses and we have to send SIGKILL. There is no great value in having the postmaster process quit sooner, and doing so can mislead onlookers into thinking that the cluster is fully terminated when actually some child processes still survive. This effect might explain recent test failures on buildfarm member hamster, wherein we failed to restart a cluster just after shutting it down with "pg_ctl stop -m immediate". I also did a bit of code review/beautification, including fixing a faulty use of the Max() macro on a volatile expression. Back-patch to 9.4. In older branches, the postmaster never waited for children to exit during immediate shutdowns, and changing that would be too much of a behavioral change. http://git.postgresql.org/pg/commitdiff/48913db887e6a41fa3f1b6cdf80ee89e38f21d9d

Ãlvaro Herrera pushed:

Peter Eisentraut pushed:

Andres Freund pushed:

  • Add missing check for wal_debug GUC. 9a20a9b2 added a new elog(), enabled when WAL_DEBUG is defined. The other WAL_DEBUG dependant messages check for the wal_debug GUC, but this one did not. While at it replace 'upto' with 'up to'. Discussion: 20150610110253.GF3832@alap3.anarazel.de Backpatch to 9.4, the first release containing 9a20a9b2. http://git.postgresql.org/pg/commitdiff/90231cd5188c43da94f58f7a839eee9286d0f864
  • Improve multixact emergency autovacuum logic. Previously autovacuum was not necessarily triggered if space in the members slru got tight. The first problem was that the signalling was tied to values in the offsets slru, but members can advance much faster. Thats especially a problem if old sessions had been around that previously prevented the multixact horizon to increase. Secondly the skipping logic doesn't work if the database was restarted after autovacuum was triggered - that knowledge is not preserved across restart. This is especially a problem because it's a common panic-reaction to restart the database if it gets slow to anti-wraparound vacuums. Fix the first problem by separating the logic for members from offsets. Trigger autovacuum whenever a multixact crosses a segment boundary, as the current member offset increases in irregular values, so we can't use a simple modulo logic as for offsets. Add a stopgap for the second problem, by signalling autovacuum whenver ERRORing out because of boundaries. Discussion: 20150608163707.GD20772@alap3.anarazel.de Backpatch into 9.3, where it became more likely that multixacts wrap around. http://git.postgresql.org/pg/commitdiff/667912aee649c3608e003568e4b47d95251b1c8c

Correctifs rejetés (à ce jour)

No one was disappointed this week :-)

Correctifs en attente

David Rowley sent in a patch to let the executor notice when multiple aggregates in a query share a transition function, executing the common ones only once per row.

David Rowley sent in another revision of a patch to improve some appendStringInfo* calls.

Petr Jelinek sent in a patch to extend CREATE EXTENSION to include its dependencies via the optional RECURSIVE keyword.

Fabien COELHO sent in another revision of a patch to fix pgbench --progress report under (very) low rate.

Tomas Vondra sent in a patch to teach the expression walker about RestrictInfo.

Amit Kapila sent in a patch to rename mapfile if backupfile not present.

Vik Fearing sent in a patch to add tab completion to psql for CREATE SEQUENCE.

Michael Paquier sent in a patch to reproduce a problem with pg_rewind.

Michael Paquier sent in a patch to make process_remote_file ignore files named as pg_xlog/xlogtemp.*.

SAWADA Masahiko sent in a patch to give the GIN function of pageinspect a consistent data type.

Fabien COELHO sent in another revision of a patch to smooth checkpoint flushing.

Tomas Vondra sent in another revision of a patch to make a better ndistinct estimator.

Brendan Jurd sent in two revisions of a patch to add a new built-in function pg_notify_queue_saturation().

Michael Paquier sent in three more revisions of a patch to improve the way TAP tests log their output using IPC::Run::run.

Michael Paquier sent in a patch to add a missing -w switch to the pg_ctl stop call in pg_regress.

Robert Haas, Tom Lane, and Dean Rasheed traded patches to fix some infelicities recently introduced in the table inheritance part of the planner.

Marti Raudsepp sent in a patch to fix pg_upgrade when postgres template1 aren't in the default database.

Petr Jelinek sent in another revision of a patch to implement tab completion in psql for TABLESAMPLE.

Ãlvaro Herrera sent in a patch to add pg_get_multixact_members() and pg_get_multixact_range().

Thomas Munro sent in a patch to fix an issue where the get_relation_info comment was out of sync with the code nearby.

Andres Freund sent in a patch to rework the way multixact truncations work with the goal of making them WAL logged.

Fabien COELHO sent in a patch to allow backslash-continuations in custom scripts.