Le calendrier pour le Postgres Open a été publié sur le site : http://postgresopen.org/

Les nouveautés des produits dérivés

  • Pgpool Global Development Group a le plaisir d'annoncer la publication de pgpool-II 3.3.0 et de pgpoolAdmin 3.3.0. Vous pouvez les télécharger aux emplacements suivants : pgpool-II-3.3.0 et pgpoolAdmin-3.3.0

Offres d'emplois autour de PostgreSQL en août

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

Tom Lane a poussé :

  • Make sure float4in/float8in accept all standard spellings of "infinity". The C99 and POSIX standards require strtod() to accept all these spellings (case-insensitively): "inf", "+inf", "-inf", "infinity", "+infinity", "-infinity". However, pre-C99 systems might accept only some or none of these, and apparently Windows still doesn't accept "inf". To avoid surprising cross-platform behavioral differences, manually check for each of these spellings if strtod() fails. We were previously handling just "infinity" and "-infinity" that way, but since C99 is most of the world now, it seems likely that applications are expecting all these spellings to work. Per bug #8355 from Basil Peace. It turns out this fix won't actually resolve his problem, because Python isn't being this careful; but that doesn't mean we shouldn't be. http://git.postgresql.org/pg/commitdiff/221e92f64c6e136e550ec2592aac3ae0d4623209
  • - Fix regexp_matches() handling of zero-length matches. We'd find the same match twice if it was of zero length and not immediately adjacent to the previous match. replace_text_regexp() got similar cases right, so adjust this search logic to match that. Note that even though the regexp_split_to_xxx() functions share this code, they did not display equivalent misbehavior, because the second match would be considered degenerate and ignored. Jeevan Chalke, with some cosmetic changes by me. http://git.postgresql.org/pg/commitdiff/d074b4e50d11768ab6da696b13d40ec05e4823fb
  • Fix contrib/cube and contrib/seg to build with bison 3.0. These modules used the YYPARSE_PARAM macro, which has been deprecated by the bison folk since 1.875, and which they finally removed in 3.0. Adjust the code to use the replacement facility, %parse-param, which is a much better solution anyway since it allows specification of the type of the extra parser parameter. We can thus get rid of a lot of unsightly casting. Back-patch to all active branches, since somebody might try to build a back branch with up-to-date tools. http://git.postgresql.org/pg/commitdiff/55cbfa5366b78d93cd1ff8c4c622b552985344f6

Gregory Stark a poussé :

Bruce Momjian a poussé :

Noah Misch a poussé :

  • Restore REINDEX constraint validation. Refactoring as part of commit 8ceb24568054232696dddc1166a8563bc78c900a had the unintended effect of making REINDEX TABLE and REINDEX DATABASE no longer validate constraints enforced by the indexes in question; REINDEX INDEX still did so. Indexes marked invalid remained so, and constraint violations arising from data corruption went undetected. Back-patch to 9.0, like the causative commit. http://git.postgresql.org/pg/commitdiff/16f38f72ab2b8a3b2d45ba727d213bb31111cea4

Fujii Masao a poussé :

Alvaro Herrera a poussé :

  • Fix a couple of inconsequential typos in new header http://git.postgresql.org/pg/commitdiff/3142cf6dd5c0308633e36fabbd13bb51bdec1ff2
  • Fix mis-indented lines. Per Coverity http://git.postgresql.org/pg/commitdiff/a59516b6311a6c2acc89448c94913ebae598f02a
  • Fix crash in error report of invalid tuple lock. My tweak of these error messages in commit c359a1b082 contained the thinko that a query would always have rowMarks set for a query containing a locking clause. Not so: when declaring a cursor, for instance, rowMarks isn't set at the point we're checking, so we'd be dereferencing a NULL pointer. The fix is to pass the lock strength to the function raising the error, instead of trying to reverse-engineer it. The result not only is more robust, but it also seems cleaner overall. Per report from Robert Haas. http://git.postgresql.org/pg/commitdiff/88c556680ca3faa40f7428c7705455d744a9859e
  • Fix old visibility bug in HeapTupleSatisfiesDirty. If a tuple is locked but not updated by a concurrent transaction, HeapTupleSatisfiesDirty would return that transaction's Xid in xmax, causing callers to wait on it, when it is not necessary (in fact, if the other transaction had used a multixact instead of a plain Xid to mark the tuple, HeapTupleSatisfiesDirty would have behave differently and *not* returned the Xmax). This bug was introduced in commit 3f7fbf85dc5b42, dated December 1998, so it's almost 15 years old now. However, it's hard to see this misbehave, because before we had NOWAIT the only consequence of this is that transactions would wait for slightly more time than necessary; so it's not surprising that this hasn't been reported yet. Craig Ringer and Andres Freund http://git.postgresql.org/pg/commitdiff/706f9dd914c64a41e06b5fbfd62d6d6dab43eeb8

Stephen Frost a poussé :

  • Allow a context to be passed in for error handling. As pointed out by Tom Lane, we can allow other users of the error handler callbacks to provide their own memory context by adding the context to use to ErrorData and using that instead of explicitly using ErrorContext. This then allows GetErrorContextStack() to be called from inside exception handlers, so modify plpgsql to take advantage of that and add an associated regression test for it. http://git.postgresql.org/pg/commitdiff/ddef1a39c6798ffae899acd08ff92329dd304085
  • Add locking around SSL_context usage in libpq. I've been working with Nick Phillips on an issue he ran into when trying to use threads with SSL client certificates. As it turns out, the call in initialize_SSL() to SSL_CTX_use_certificate_chain_file() will modify our SSL_context without any protection from other threads also calling that function or being at some other point and trying to read from SSL_context. To protect against this, I've written up the attached (based on an initial patch from Nick and much subsequent discussion) which puts locks around SSL_CTX_use_certificate_chain_file() and all of the other users of SSL_context which weren't already protected. Nick Phillips, much reworked by Stephen Frost Back-patch to 9.0 where we started loading the cert directly instead of using a callback. http://git.postgresql.org/pg/commitdiff/aad2a630b1b163038ea904e16a59e409020f5828
  • Improve handling of pthread_mutex_lock error case. We should really be reporting a useful error along with returning a valid return code if pthread_mutex_lock() throws an error for some reason. Add that and back-patch to 9.0 as the prior patch. Pointed out by Alvaro Herrera http://git.postgresql.org/pg/commitdiff/8359ed806f3300b79f110f1ac216c58c0732d05c

Robert Haas a poussé :

Kevin Grittner a poussé :

Correctifs rejetés (à ce jour)

  • No one was disappointed this week

Correctifs en attente

  • Andrew (RhodiumToad) Gierth and Gregory Stark traded patches to clean up the grammar pursuant to discussion around the WITH ORDINALITY patch.
  • Andrew Tipton sent in a patch to add various JSON manipulation functions.
  • Amit Kapila sent in another revision of a patch to add ALTER SYSTEM.
  • Pavel Stehule sent in a patch to allow database owners to cancel the queries of roles which are not superuser.
  • Andres Freund sent in a PoC patch to allow computing VARSIZE_ANY(PTR) during debugging.
  • Stefan Radomski sent in a patch to reserve connections for replication roles.
  • Gregory Stark sent in a patch to improve the performance of WITH ORDINALITY.
  • Ivan Lezhnjov IV sent in another revision of a patch to fix the documentation of backups.
  • Stefan Radomski sent in another revision of a patch to allow throttling backups.
  • MauMau sent in two revisions of a patch to fix a bug where disk space in pg_xlog increases during archive recovery.
  • Fujii Masao sent in a patch to fix a bug which caused an assertion failure in immediate shutdown mode.
  • Alvaro Herrera sent in a WIP patch to change the behavior of IS NULL in the catalog.
  • Dimitri Fontaine sent in two more revisions of a patch to implement EXTENSION TEMPLATEs.
  • Craig Ringer sent in a patch to fix a bug where FOR SHARE|UPDATE NOWAIT will still block if they have to follow a ctid chain.
  • Antonin Houska sent in a WIP patch to do partial matches using range key entries.
  • Alvaro Herrera sent in a patch to extend SLRU in a way that prevents a pg_upgrade failure.
  • Tomonari Katsumata sent in another revision of a patch to fix fast promotion of a replica to master.
  • Ian Lawrence Barwick sent in two revisions of a patch to show the object schema in verbose output in pg_dump/pg_restore.
  • -- Sent via pgsql-announce mailing list (pgsql-announce@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-announce