Les versions correctives 9.3.1, 9.2.5, 9.1.10, 9.0.14 et 8.4.18 ont été publiées. La mise à jour peut attendre la prochaine coupure programmée, à moins que vous ne soyiez directement touché par les problèmes décrits ci-après : http://www.postgresql.org/about/news/1487/

La deuxième CommitFest du cycle de la version 9.4 se terminera le 15 octobre à minuit. Relisez ces patchs !

L'appel à conférenciers du monde entier pour le PgDay équatorien, intégré à la Feria Internacional del Libro à Quito, Équateur, a été lancé. Écrivez à ecpug <AT> postgresql <DOT> org. Détails (en espagnol) ci-après : https://wiki.postgresql.org/wiki/PGDay_Ecuador_2013

Les nouveautés des produits dérivés

Offres d'emplois autour de PostgreSQL en octobre

PostgreSQL Local

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

Kevin Grittner a poussé :

  • Eliminate xmin from hash tag for predicate locks on heap tuples. If a tuple was frozen while its predicate locks mattered, read-write dependencies could be missed, resulting in failure to detect conflicts which could lead to anomalies in committed serializable transactions. This field was added to the tag when we still thought that it was necessary to carry locks forward to a new version of an updated row. That was later proven to be unnecessary, which allowed simplification of the code, but elimination of xmin from the tag was missed at the time. Per report and analysis by Heikki Linnakangas. Backpatch to 9.1. http://git.postgresql.org/pg/commitdiff/c01262a82484106111a81dca8c922fd5670b644d
  • Allow drop-index-concurrently-1 test to run at any isolation level. It previously reported failure at REPEATABLE READ and SERIALIZABLE transaction isolation levels for make installcheck. http://git.postgresql.org/pg/commitdiff/31a877f18bdf60dd1dfe92e7502469ed4c40d75b
  • Add record_image_ops opclass for matview concurrent refresh. REFRESH MATERIALIZED VIEW CONCURRENTLY was broken for any matview containing a column of a type without a default btree operator class. It also did not produce results consistent with a non- concurrent REFRESH or a normal view if any column was of a type which allowed user-visible differences between values which compared as equal according to the type's default btree opclass. Concurrent matview refresh was modified to use the new operators to solve these problems. Documentation was added for record comparison, both for the default btree operator class for record, and the newly added operators. Regression tests now check for proper behavior both for a matview with a box column and a matview containing a citext column. Reviewed by Steve Singer, who suggested some of the doc language. http://git.postgresql.org/pg/commitdiff/f566515192461acd8d9c232f48ddac3fc965cfd8
  • Fix bug in record_image_ops on big endian machines. The buildfarm pointed out the problem. Fix based on suggestion by Robert Haas. http://git.postgresql.org/pg/commitdiff/15e46fd1dd77d908d73c48d601694a6809d18976
  • Fix several possibly non-portable gaffs in record_image_ops. Sparc machines in the buildfarm were made happy by the previous fix, but PowerPC machines still are still failing. Hopefully this will cure that. http://git.postgresql.org/pg/commitdiff/4cbb646334b3b998a29abef0d57608d42097e6c9

Robert Haas a poussé :

Peter Eisentraut a poussé :

Heikki Linnakangas a poussé :

  • Fix bugs in SSI tuple locking. 1. In heap_hot_search_buffer(), the PredicateLockTuple() call is passed wrong offset number. heapTuple->t_self is set to the tid of the first tuple in the chain that's visited, not the one actually being read. 2. CheckForSerializableConflictIn() uses the tuple's t_ctid field instead of t_self to check for exiting predicate locks on the tuple. If the tuple was updated, but the updater rolled back, t_ctid points to the aborted dead tuple. Reported by Hannu Krosing. Backpatch to 9.1. http://git.postgresql.org/pg/commitdiff/81fbbfe3352d3965ee3d8eaafe164b2335c43f72
  • TYPEALIGN doesn't work on int64 on 32-bit platforms. The TYPEALIGN macro, and the related ones like MAXALIGN, don't work with values larger than intptr_t, because TYPEALIGN casts the argument to intptr_t to do the arithmetic. That's not a problem when dealing with pointers or lengths or offsets related to pointers, but the XLogInsert scaling patch added a call to MAXALIGN with an XLogRecPtr argument. To fix, add wider variants of the macros, called TYPEALIGN64 and MAXALIGN64, which are just like the existing variants but work with uint64 instead of intptr_t. Report and patch by David Rowley, analysis by Andres Freund. http://git.postgresql.org/pg/commitdiff/5962519b362d28ef02bc8ec135b9bf9b9a168263

Bruce Momjian a poussé :

Andrew Dunstan a poussé :

Alvaro Herrera a poussé :

  • Use $(PERL) to invoke duplicate_oids. Per buildfarm failure reported by smilodon http://git.postgresql.org/pg/commitdiff/ada01014d4739120361fb96e3f91e2fd6791d6b8
  • Rework SSL renegotiation code. The existing renegotiation code was home for several bugs: it might erroneously report that renegotiation had failed; it might try to execute another renegotiation while the previous one was pending; it failed to terminate the connection if the renegotiation never actually took place; if a renegotiation was started, the byte count was reset, even if the renegotiation wasn't completed (this isn't good from a security perspective because it means continuing to use a session that should be considered compromised due to volume of data transferred.) The new code is structured to avoid these pitfalls: renegotiation is started a little earlier than the limit has expired; the handshake sequence is retried until it has actually returned successfully, and no more than that, but if it fails too many times, the connection is closed. The byte count is reset only when the renegotiation has succeeded, and if the renegotiation byte count limit expires, the connection is terminated. This commit only touches the master branch, because some of the changes are controversial. If everything goes well, a back-patch might be considered. Per discussion started by message 20130710212017.GB4941@eldon.alvh.no-ip.org http://git.postgresql.org/pg/commitdiff/31cf1a1a43c45e53d9bb3134c07f92e722f097f9

Correctifs rejetés (à ce jour)

  • No one was disappointed this week

Correctifs en attente

  • Dimitri Fontaine sent in another revision of a patch to implement PL support for EVENT TRIGGERS.
  • SAKAMOTO Masahiko sent in another revision of a patch to enable WAL-based fail-back without fresh backup.
  • Heikki Linnakangas sent in two more revisions of a patch to improve GIN indexes by adding information to same.
  • Pavel Stehule sent in another revision of a patch to allow fast update of arrays with fixed length in PL/pgsql.
  • Robert Haas sent in a patch to ensure that certain cases are always in a transaction, incurring a cache hit if needed.
  • Andrew (RhodiumToad) Gierth sent in another revision of a patch to implement UNNEST with multiple arguments and TABLE with multiple SRFs.
  • David Fetter sent in a patch to allow CREATE FOREIGN TABLE to take LIKE as a parameter.
  • Kevin Grittner sent in another revision of a patch to fix the SSI freezing bug.
  • Marc Cousin sent in a patch to fix an issue in contrib/lo triggers.
  • Andres Freund sent in another flock of patches intended to be infrastructure for logical changeset generation.
  • Pavel Stehule sent in a patch to allow RAISE ... WHEN in PL/pgsql as an alternative to the wordier IF [EXCEPTION_TYPE] THEN RAISE ... END IF construct.
  • Michael Paquier sent in a patch to pre-fix some comments in the code in preparation for REINDEX CONCURRENTLY.
  • Stefan Radomski sent in two more revisions of a patch to allow reserving connections for replication roles, as distinct from those reserved for superuser.
  • Antonin Houska sent in another revision of a patch to enable throttling backups.
  • Mark Kirkwood sent in another revision of a patch to enable block sampling.
  • Sameer Thakur sent in a patch to add documentation for session_start and introduced fields and corrects documentation for queryid to be query_id in the pg_stat_statements view.
  • Heikki Linnakangas sent in another revision of a patch to extend the CUBE extension support to points.
  • Pavel Stehule and Alvaro Herrera traded patches to implement a simple date constructor for numeric values.
  • Hari Babu sent in a patch to fix an issue where vacuum is not happening on a heavily modified big table even if the dead tuples are more than configured threshold. This was caused by the fact that the number of dead tuples is set to zero and no accounting was made for dead tuples created as the vacuum ran.
  • Michael Paquier sent in a patch to add worker_spi_terminate to contrib/worker_spi.
  • Peter Geoghegan sent in another revision of a patch to implement INSERT...ON DUPLICATE KEY LOCK FOR UPDATE.