Les nouveautés des produits dérivés

  • dbForge Data Compare pour PostgreSQL, un outil de différenciation et de synchronisation de données pour PostgreSQL qui permet de passer en revue toutes les différences entre des tables et exécuter le script automatiquement généré pour résoudre ces différends  http://www.devart.com/dbforge/postgresql/datacompare/
  • pgFormatter v1.1, un outil de formatage/mise en forme/coloration syntaxique en ligne gérant les mots clefs des standards SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011 et ceux de PostgreSQL http://sqlformat.darold.net/
  • PG Jobmon version 1.0.0, une extension pour logger hors du système transactionnel et surveiller l'exécution de fonctions : https://github.com/omniti-labs/pg_jobmon

Offres d'emplois autour de PostgreSQL en décembre

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

Simon Riggs a poussé :

Tom Lane a poussé :

  • Fix some minor issues in view pretty-printing. Code review for commit 2f582f76b1945929ff07116cd4639747ce9bb8a1: don't use a static variable for what ought to be a deparse_context field, fix non-multibyte-safe test for spaces, avoid useless and potentially O(N2) (though admittedly with a very small constant) calculations of wrap positions when we aren't going to wrap. http://git.postgresql.org/pg/commitdiff/3f88b080030682adf359248c9cb7f8b2068a539e

Bruce Momjian a poussé :

Peter Eisentraut a poussé :

Alvaro Herrera a poussé :

  • Remove unused NextLogPage macro. Commit 061e7efb1b did away with its last caller, but neglected to remove the actual definition. Author: Andres Freund http://git.postgresql.org/pg/commitdiff/eaa1f7220ae83997b56adcae1fbb7b2e92bfc050
  • Assign InvalidXLogRecPtr instead of MemSet(0) For consistency. Author: Andres Freund http://git.postgresql.org/pg/commitdiff/24eca7977ed208de33791af8890975ffcf086598
  • Remove obsolete XLogRecPtr macros. This gets rid of XLByteLT, XLByteLE, XLByteEQ and XLByteAdvance. These were useful for brevity when XLogRecPtrs were split in xlogid/xrecoff; but now that they are simple uint64's, they are just clutter. The only downside to making this change would be ease of backporting patches, but that has been negated by other substantive changes to the involved code anyway. The clarity of simpler expressions makes the change worthwhile. Most of the changes are mechanical, but in a couple of places, the patch author chose to invert the operator sense, making the code flow more logical (and more in line with preceding comments). Author: Andres Freund Eyeballed by Dimitri Fontaine and Alvaro Herrera http://git.postgresql.org/pg/commitdiff/5ab3af46ddd2f2c2b248f1ffdb688b394d4bb387

Robert Haas a poussé :

Heikki Linnakangas a poussé :

  • Keep timeline history files restored from archive in pg_xlog. The cascading standby patch in 9.2 changed the way WAL files are treated when restored from the archive. Before, they were restored under a temporary filename, and not kept in pg_xlog, but after the patch, they were copied under pg_xlog. This is necessary for a cascading standby to find them, but it also means that if the archive goes offline and a standby is restarted, it can recover back to where it was using the files in pg_xlog. It also means that if you take an offline backup from a standby server, it includes all the required WAL files in pg_xlog. However, the same change was not made to timeline history files, so if the WAL segment containing the checkpoint record contains a timeline switch, you will still get an error if you try to restart recovery without the archive, or recover from an offline backup taken from the standby. With this patch, timeline history files restored from archive are copied into pg_xlog like WAL files are, so that pg_xlog contains all the files required to recover. This is a corner-case pre-existing issue in 9.2, but even more important in master where it's possible for a standby to follow a timeline switch through streaming replication. To make that possible, the timeline history files must be present in pg_xlog. http://git.postgresql.org/pg/commitdiff/60df192aea0e6458f20301546e11f7673c102101

Correctifs rejetés (à ce jour)

  • Pas de déception cette semaine :-)

Correctifs en attente

  • Dimitri Fontaine sent in four more revisions of a patch to add EVENT triggers.
  • Pavel Stehule sent in a patch to add a regrole type.
  • Andrew Dunstan sent in another WIP patch for the JSON API.
  • Peter Bex sent in a patch intended to improve password hashing by adding bcrypt.
  • Alvaro Herrera and Heikki Linnakangas traded patches to fix bgworkers in the EXEC_BACKEND case.
  • Kyotaro HORIGUCHI sent in two more revisions of a patch to reduce the amount of WAL generated during update operations.
  • Alvaro Herrera sent in another revision of a patch to implement foreign key locks.
  • Heikki Linnakangas sent in a patch to fix a performance regression in dynamic SQL by eliminating some unneeded copying of the parse- and plan trees.
  • Pavel Stehule sent in a patch to implement SQL:2011 named parameters.
  • Dan Farina sent in four revisions of a patch to establish a maximum under-estimate of the number of calls for a given pg_stat_statements entry. That means the number of calls to the canonical form of the query is between 'calls' and 'calls + calls_underest'.
  • Pavel Stehule sent in another revision of a patch to enhance error fields in PL/pgsql.
  • Tom Lane sent in a patch to make view dump/restore safe at the column-alias level.
  • Craig Ringer sent in a patch to change the Windows build docs to point to flex and bison from msys.