La planète francophone de PostgreSQL

PostgreSQL 9.0 RC1

2010-08-31T20:19:50+00:00

La première « release candidate » de PostgreSQL 9.0 est désormais publiée.

Plus vite vous la téléchargerez et la testerez, plus vite nous aboutirons à la version finale. Tous les bogues connus doivent être corrigés. C'est pourquoi nous demandons aux utilisateurs de remonter rapidement tout bogue qu'ils pourraient rencontrer.

Du fait d'une modification dans le catalogue système, un initdb et un rechargement de la base sont nécessaires pour les mises à jour depuis les versions bêta de la 9.0. Cela peut être considéré comme une opportunité de tester pg_upgrade. N'oubliez pas de reporter vos résultats.

Si vous pouvez nous aider dans les tests, merci de consulter la page consacrée aux tests : http://wiki.postgresql.org/wiki/HowToBetaTest.

Aucune modifications dans les commandes, les interfaces ou les API n'est attendue entre cette RC et la version finale. Les applications qui utiliseront la version 9.0 peuvent (devraient) être testées au regard de la version 9.0rc1.

Les rapports de bogue décideront d'une éventuelle nouvelle RC.

Le code source, et les installateurs binaires pour diverses plateformes sont disponibles sur le site Web de PostgreSQL :

Source :

 http://www.postgresql.org/ftp/source/v9.0rc1

Installateur Un-Clic incluant les binaires Win64 :

 http://www.enterprisedb.com/products/pgdownload.do

Binaires pour les autres plateformes :

 http://www.postgresql.org/ftp/binary/v9.0rc1

Notes de version :

 http://developer.postgresql.org/pgdocs/postgres/release-9-0.html

Participer aux tests :

 http://www.postgresql.org/developer/beta

Quand sortira la version finale de PostgreSQL 9.0 ?

2010-08-31T07:16:00+00:00

Alors que la sortie de la première version candidate de PostgreSQL 9.0 RC1 vient de sortir, l'impatience augmente et les questions commencent à fuser : "Quand pourrons-nous utiliser la version 9.0 en production ?" . Évidement, il est impossible de donner une réponse précise à cette question puisque le processus de livraison des versions de PostgreSQL n'est pas basé sur un agenda strict (comme Ubuntu par exemple ) mais sur la qualité et quantité de tests réalisés...

La meilleure réponse est donc : "Testez la version RC de PostgreSQL 9.0 chez vous. Dès aujourd"hui ! En cas de problème, envoyez un rapport de bug aux développeurs. C'est une façon simple de participer à la communauté Postgres et cela de sortir la version stable rapidement.

Toutefois, cette réponse n'est pas toujours satisfaisante pour les plus impatients. On peut alors s'amuser à prédire la date de sortie, non pas avec une boule de crystal mais en analysant les statistiques de sorties des 5 dernières versions (de 8.0 à 8.4 ). J'ai donc repris toutes les dates de sortie des versions béta et RC depuis le 9 aout 2004. On obtient alors le graphe suivant :

Il est frappant de constater des similitudes entre la version 8.0 et la 9.0 : pour ces deux versions la période entre la version beta1 et la version RC1 dure environ 118 jours (116 pour la 8.0, 120 pour la 9.0), tandis que pour les versions 8.1, 8.2, 8.3 et 8.4 cette période dure entre 60 et 90 jours... Rien de très étonnant à tout cela ! Le changement du premier chiffre indique un changement de génération et l'arrivée de fonctionnalités ayant un impact très fort sur l'utilisation de Postgres ( par exemple: le portage sous windows pour la version 8.0 , le Hot Standby/Streaming replication pour la 9.0 ). Ainsi il est logique que le passage de la version 7 à 8 et de 8 à 9 demande plus de tests et de corrections de bugs....

Maintenant, utilisons les données que nous avons sur le cycle de release de la version 8.0 pour prédire la sortie de la version finale de PostgreSQL 9.0 : Il a fallu 47 jours entre la sortie de la version 8.0RC1 et la version 8.0.0 finale. Si l'on suit la corrélation de rythme avec la version 8.0, alors la période de RC devrait durer 49 jours. La date de sortie finale serait alors 18 octobre 2010 !

Bien sur, ce n'est qu'une déduction abstraite et naïve... Le processus de livraison de PostgreSQL est bien trop complexe pour être modélisé de cette manière et je n'ai pas la prétention de lire dans le marc de café

Toutefois ce petit exercice de statistiques montre que le projet PostgreSQL a une certaine constance dans sa progression et dans son fonctionnement.

Au passage, on peut également souligner que les périodes de tests de PostgreSQL sont très courtes ( entre 75 et 160 jours ). Pour un logiciel de cette ampleur ( 500 000 lignes de codes) c'est exceptionnel ! A titre d'exemple, la période de test d'Oracle 11g a duré plus de 10 mois ( sept 06 -> juillet 07 )... Là encore, l'explication est assez logique : le code de Postgres est ouvert et les beta-testeurs sont nombreux et réactifs.

Bref pour participer au projet PostgreSQL, vous savez ce qu'il vous reste à faire ! Téléchargez la version 9.0rc1, Testez-là et Signalez les éventuels incidents !

PS / Pour ceux qui voudraient vérifier les chiffres le tableau OOo est là : http://nawak.taadeem.net/9.0.ods

Nouvelles hebdomadaires de PostgreSQL - 29 août 2010

2010-08-30T09:13:23+00:00

Sortie prochaine de PostgreSQL 9.0 RC1. Plus vous testez, plus tôt la 9.0.0 finale sortira ! http://www.postgresql.org/developer/beta/

Les nouveautés des produits dérivés

AnyDAC v 4.0.1, une boîte à outil pour Delphi : http://www.da-soft.com/anydac/
CSV Loader 2.1, un outil Java pour charger et fusionner des fichiers CSV dans PostgreSQL : http://csvloader.sourceforge.net/
pgpool-II 3.0beta2, un gestionnaire de connexions et bien d'avantage : http://pgfoundry.org/projects/pgpool/
PostgreSQL PHP Generator 10.8, une interface graphique pour générer du PHP à partir d'objets PostgreSQL "select" : http://www.sqlmaestro.com/products/postgresql/phpgenerator/

Offres d'emplois autour de PostgreSQL en août

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

PostgreSQL Local

L'appel à conférenciers pour la "West" est lancé jusqu'au 5 septembre 2010. Détails sur : http://www.postgresqlconference.org/
L'appel à conférenciers pour le PGDay.EU 2010, tenu du 6 au 8 décembre à Stuttgart (All.), est lancé : http://2010.pgday.eu/callforpapers

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

Tom Lane a commité :

Make an editorial pass over the 9.0 release notes. This is mostly about grammar, style, and presentation, though I did find a few small factual errors.
In pgsql/contrib/pg_archivecleanup/pg_archivecleanup.c, make pg_archivecleanup log messages more consistent. Erik Rijkers
Marginal code cleanup for streaming replication. There is no reason that proc.c should have to get involved in this dirty hack for letting the postmaster know which children are walsenders. Revert that file to the way it was, and confine the kluge to pmsignal.c and postmaster.c.
In pgsql/src/backend/commands/explain.c, make EXPLAIN show the function call expression of a FunctionScan plan node, but only in VERBOSE mode. Per discussion.
In pgsql/doc/src/sgml/release-9.0.sgml, further editing of release notes.
In pgsql/doc/src/sgml/release-9.0.sgml, update 9.0 release notes for changes since beta4. Note: as usual, bug fixes that were also applied in back branches are not considered material to include in a new major release's notes.
In pgsql/src/bin/psql/command.c, avoid passing signed chars to <ctype.h> functions ... same old portability mistake as always. Per buildfarm member pika.
In pgsql/doc/src/sgml/unaccent.sgml, docs review for unaccent: fix grammar, markup, etc.
In pgsql/src/backend/port/sysv_shmem.c, improve hint message for ENOMEM failure from shmget(). It turns out that some platforms return ENOMEM for a request that violates SHMALL, whereas we were assuming that ENOSPC would always be used for that. Apparently the latter is a Linuxism while ENOMEM is the BSD tradition. Extend the ENOMEM hint to suggest that raising SHMALL might be needed. Per gripe from A.M. Backpatch to 9.0, but not further, because this doesn't seem important enough to warrant creating extra translation work in the stable branches. (If it were, we'd have figured this out years ago.)
In a bit more., document filtering dictionaries in textsearch.sgml. While at it, copy-edit the description of prefix-match marker support in synonym dictionaries, and clarify the description of the default
In pgsql/config/prep_buildtree, don't auto-create the subdirectories holding built documentation in a VPATH build tree. If we actually build the docs in the VPATH tree, those dirs will get created then; but if they're present and empty, they capture the vpathsearch searches in "make install", preventing installation of prebuilt docs that might exist in the source tree. Per bug #5595 from Dmtiriy Igrishin. Fix based on idea from Peter Eisentraut.
In pgsql/src/backend/executor/execQual.c, fix ExecMakeTableFunctionResult to verify that all rows returned by a SRF returning "record" actually do have the same rowtype. This is needed because the parser can't realistically enforce that they will all have the same typmod, as seen in a recent example from David Wheeler. Back-patch to 8.0, which is as far back as we have the notion of RECORD subtypes being distinguished by typmod. Wheeler's example depends on 8.4-and-up features, but I suspect there may be ways to provoke similar failures before 8.4.
Update time zone data files to tzdata release 2010l: DST law changes in Egypt and Palestine. Added new names for two Micronesian timezones: Pacific/Chuuk is now preferred over Pacific/Truk (and the preferred abbreviation is CHUT not TRUT) and Pacific/Pohnpei is preferred over Pacific/Ponape. Historical corrections for Finland.
In pgsql/doc/src/sgml/ddl.sgml, explain automatic creation (or lack of it) of indexes for the various types of constraints. Kevin Grittner.
Document the existence of the socket lock file under unix_socket_directory, which is perhaps not a terribly good spot for it but there doesn't seem to be a better place. Also add a source-code comment pointing out a couple reasons for having a separate lock file. Per suggestion from Greg Smith.
In pgsql/doc/src/sgml/libpq.sgml, remove obsolete remark that PQprepare() is more flexible than PREPARE. Spotted by Dmitriy Igrishin. Back-patch to 8.2, which is when the PREPARE statement was improved to allow parameter types to be omitted.
Reduce PANIC to ERROR in some occasionally-reported btree failure cases. This patch changes _bt_split() and _bt_pagedel() to throw a plain ERROR, rather than PANIC, for several cases that are reported from the field from time to time: 1. right sibling's left-link doesn't match; 2. PageAddItem failure during _bt_split(); 3. parent page's next child isn't right sibling during _bt_pagedel(). In addition the error messages for these cases have been made a bit more verbose, with additional values included. The original motivation for PANIC here was to capture core dumps for subsequent analysis. But with so many users whose platforms don't capture core dumps by default, or who are unprepared to analyze them anyway, it's hard to justify a forced database restart when we can fairly easily detect the problems before we've reached the critical sections where PANIC would be necessary. It is not currently known whether the reports of these messages indicate well-hidden bugs in Postgres, or are a result of storage-level malfeasance; the latter possibility suggests that we ought to try to be more robust even if there is a bug here that's ultimately found. Backpatch to 8.2. The code before that is sufficiently different that it doesn't seem worth the trouble to back-port further.

ITAGAKI Takahiro a commité :

Add string functions: concat(), concat_ws(), left(), right(), and reverse(). Pavel Stehule, reviewed by me.

Bruce Momjian a commité :

In pgsql/doc/src/sgml/config.sgml, update autovacuum_freeze_max_age documentation to mention that the default is low because of pg_clog file removal. Backpatch to 9.0.X.
In pgsql/doc/src/sgml/release-9.0.sgml, clarifications for 9.0 release notes Josh Berkus
In pgsql/doc/src/sgml/high-availability.sgml, fix awkward wording in Incrementally Updated Backups docs. Backpatch to 9.0.X.
In pgsql/doc/src/sgml/release-9.0.sgml, update release notes, per comments from Simon Riggs.
In pgsql/doc/src/sgml/high-availability.sgml, remove docs for "Incrementally Updated Backups" because it was of questionable reliability; information moved to a wiki: http://wiki.postgresql.org/wiki/Incrementally_Updated_Backups Backpatch to 9.0.

Peter Eisentraut a commité :

In pgsql/src/Makefile.global.in, when in automatic dependency mode, never delete any intermediate files automatically. Otherwise, the following could happen: When starting from a clean source tree, the first build would delete the intermediate file, but also create the dependency file, which mentions the intermediate file, thus making it non-intermediate. The second build will then need to rebuild the now non-intermediate missing file. So the second build will do work even though nothing had changed. One place where this happens is the .c -> .o -> .so chain for some contrib modules.
In pgsql/doc/src/sgml/catalogs.sgml, add missing description of reloftype field.
In pgsql/src/pl/plpython/plpython.c, catch null pointer returns from PyCObject_AsVoidPtr and PyCObject_FromVoidPtr. This is reproducibly possible in Python 2.7 if the user turned PendingDeprecationWarning into an error, but it's theoretically also possible in earlier versions in case of exceptional conditions. Backpatched to 8.0.
Translation updates for 9.0rc1.
Small refactoring of makeVar() from a TargetEntry.

Alvaro Herrera a commité :

In pgsql/src/backend/access/transam/xlog.c, remove duplicate translatable phrase.
Improve wording for privilege description on certain failure messages; the original misleadingly suggests that only access is meant, causing confusion. Per recent trouble report by Robert McGehee on pgsql-admin.

Marc Fournier a commité :

tag rc1 ... final stretch ...

Robert Haas a commité :

Rewrite comment code for better modularity, and add necessary locking. Review by Alvaro Herrera, KaiGai Kohei, and Tom Lane.
In pgsql/src/backend/catalog/objectaddress.c, insert additional compiler placation into objectaddress.c. Peter Eisentraut reports that some bits of the "address" variable in get_object_address() give "may be used uninitialized" warnings; this likes the only excuse his compiler could have for thinking that's possible.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

Andrew Dunstan sent in a WIP patch to allow enums to be extended.
Boxuan Zhai sent in another revisions of the patch to add MERGE, this time with support for table inheritance.
Bruce Momjian sent in a doc patch for incrementally updated backups.
Magnus Hagander sent in a patch which handles a Windows failure case.
KaiGai Kohei sent in another revision of the patch to add a security hook on authorization.
Zoltan Boszormenyi sent in a patch to fix ECPG's handling of mixed-case cursor names.
Heikki Linnakangas sent in a patch to add latches to the back-end.
Andrew Dunstan sent in another WIP patch to implement extensible enums.
Heikki Linnakangas sent in a patch intended to speed up parts of COPY.
Alexander Korotkov sent in a patch to add a levenshtein_less_equal function to contrib/fuzzystrmatch.
Thom Brown sent in a doc patch to fix some inconsistent markup.
Kevin Grittner sent in another revision of the SIREAD patch for true serializability, along with one which enables true serializability for GiST indexes.

Nouvelles hebdomadaires de PostgreSQL - 22 août 2010

2010-08-28T09:36:31+00:00

L'appel à conférenciers pour le PGDay.EU 2010, tenu du 6 au 8 décembre à Stuttgart (All.), est lancé : http://2010.pgday.eu/callforpapers

Les nouveautés des produits dérivés

pgpool-II 3.0beta1, un gestionnaire de connexions et bien d'avantage : http://pgfoundry.org/projects/pgpool/

Offres d'emplois autour de PostgreSQL en août

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

PostgreSQL Local

L'appel à conférenciers pour la "West" est lancé jusqu'au 5 septembre 2010. Détails sur : http://www.postgresqlconference.org/

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.

(lien vers l'article original)

Correctifs appliqués

Tom Lane a commité :

In pgsql/src/backend/utils/init/miscinit.c, arrange to fsync the contents of lockfiles (both postmaster.pid and the socket lockfile) when writing them. The lack of an fsync here may well explain two different reports we've seen of corrupted lockfile contents, which doesn't particularly bother the running server but can prevent a new server from starting if the old one crashes. Per suggestion from Alvaro Herrera. Back-patch to all supported versions.
Add missing handling of PlannedStmt.transientPlan in copyfuncs/outfuncs. _outPlannedStmt is only debug support, so the omission there was not very serious, but the omission in _copyPlannedStmt is a real bug. The consequence would be that a copied plan tree would never be marked as a transient plan, so that we would forget we ought to replan it after some not-yet-ready index becomes ready for use. This might explain some past complaints about indexes created with CREATE INDEX CONCURRENTLY not being used right away. Problem spotted by Yeb Havinga. Back-patch to 8.3, where the field was added.
Fix failure of "ALTER TABLE t ADD COLUMN c serial" when done by non-owner. The implicitly created sequence was created as owned by the current user, who could be different from the table owner, eg if current user is a superuser or some member of the table's owning role. This caused sanity checks in the SEQUENCE OWNED BY code to spit up. Although possibly we don't need those sanity checks, the safest fix seems to be to make sure the implicit sequence is assigned the same owner role as the table has. (We still do all permissions checks as the current user, however.) Per report from Josh Berkus. Back-patch to 9.0. The bug goes back to the invention of SEQUENCE OWNED BY in 8.2, but the fix requires an API change for DefineRelation(), which seems to have potential for breaking third-party code if done in a minor release. Given the lack of prior complaints, it's probably not worth fixing in the stable branches.
Rename utf2ucs() to utf8_to_unicode(), and export it so it can be used elsewhere. Similarly rename the version in mbprint.c, not because this affects anything but just to keep the two copies in exact sync. There was some discussion of having only one copy in src/port/ instead, but this function is so small and unlikely to change that that seems like overkill. Slightly editorialized version of a patch by Joseph Adams. (The bug-fix aspect of his patch was applied separately, and back-patched.)
In pgsql/src/backend/executor/nodeModifyTable.c, reset the per-output-tuple exprcontext each time through the main loop in ExecModifyTable(). This avoids memory leakage when trigger functions leave junk behind in that context (as they more or less must). Problem and solution identified by Dean Rasheed. I'm a bit concerned about the longevity of this solution --- once a plan can have multiple ModifyTable nodes, we are very possibly going to have to do something different. But it should hold up for 9.0.
In pgsql/src/backend/commands/trigger.c, fix possible corruption of AfterTriggerEventLists in subtransaction rollback. afterTriggerInvokeEvents failed to adjust events->tailfree when truncating the last chunk of an event list. This could result in the data being "de-truncated" by afterTriggerRestoreEventList during a subsequent subtransaction abort. Even that wouldn't kill us, because the re-added data would just be events marked DONE --- unless the data had been partially overwritten by new events. Then we might crash, or in any case misbehave (perhaps fire triggers twice, or fire triggers with the wrong event data). Per bug #5622 from Thue Janus Kristensen. Back-patch to 8.4 where the current trigger list representation was introduced.
In pgsql/src/backend/storage/buffer/localbuf.c, allocate local buffers in a context of their own, rather than dumping them into TopMemoryContext. This makes no functional difference, but makes it easier to see what the space is being used for in MemoryContextStats dumps. Per a recent example in which I was surprised by the size of TopMemoryContext.
In pgsql/src/pl/plpgsql/src/pl_exec.c, be a bit less cavalier with both the code and the comment for UNKNOWN fix.
In pgsql/src/pl/plpgsql/src/pl_exec.c, keep exec_simple_check_plan() from thinking "SELECT foo INTO bar" is simple. It's not clear if this situation can occur in plpgsql other than via the EXECUTE USING case Heikki illustrated, which I will shortly close off. However, ignoring the intoClause if it's there is surely wrong, so let's patch it for safety. Backpatch to 8.3, which is as far back as this code has a PlannedStmt to deal with. There might be another way to make an equivalent test before that, but since this is just preventing hypothetical bugs, I'm not going to obsess about it.
In pgsql/src/pl/plpgsql/src/gram.y, allow USING and INTO clauses of plpgsql's EXECUTE to appear in either order. Aside from being more forgiving, this prevents a rather surprising misbehavior when the "wrong" order was used: the old code didn't throw a syntax error, but absorbed the INTO clause into the last USING expression, which then did strange things downstream. Intentionally not changing the documentation; we'll continue to advertise only the "standard" clause order. Backpatch to 8.4, where the USING clause was added to EXECUTE.
Bring some sanity to the trace_recovery_messages code and docs. Per gripe from Fujii Masao, though this is not exactly his proposed patch. Categorize as DEVELOPER_OPTIONS and set context PGC_SIGHUP, as per Fujii, but set the default to LOG because higher values aren't really sensible (see the code for trace_recovery()). Fix the documentation to agree with the code and to try to explain what the variable actually does. Get rid of no-op calls trace_recovery(LOG), which accomplish nothing except to demonstrate that this option confuses even its author.
Avoid saying "random" when randomness is not actually meant. Per Thom Brown.
In pgsql/src/backend/parser/gram.y, add missing processing of OptTemp in CREATE IF NOT EXISTS variant for typed tables. Noted by Robert Haas.
In pgsql/src/bin/pg_dump/pg_backup_archiver.c, improve parallel restore's ability to cope with selective restore (-L option). The original coding tended to break down in the face of modified restore orders, as shown in bug #5626 from Albert Ullrich, because it would flip over into parallel-restore operation too soon. That causes problems because we don't have sufficient dependency information in dump archives to allow safe parallel processing of SECTION_PRE_DATA items. Even if we did, it's probably undesirable to allow that to override the commanded restore order. To fix the problem of omitted items causing unexpected changes in restore order, tweak SortTocFromFile so that omitted items end up at the head of the list not the tail. This ensures that they'll be examined and their dependencies will be marked satisfied before we get to any interesting items. In HEAD and 9.0, we can easily change restore_toc_entries_parallel so that all SECTION_PRE_DATA items are guaranteed to be processed in the initial serial-restore loop, and hence in commanded order. Only DATA and POST_DATA items are candidates for parallel processing. For them there might be variations from the commanded order because of parallelism, but we should do it in a safe order thanks to dependencies. In 8.4 it's much harder to make such a guarantee. I settled for not letting the initial loop break out into parallel processing mode if it sees a DATA/POST_DATA item that's not to be restored; this at least prevents a non-restorable item from causing premature exit from the loop. This means that 8.4 will be more likely to fail given a badly-ordered -L list than 9.x, but we don't really promise any such thing will work anyway.
In pgsql/src/backend/utils/adt/arrayfuncs.c, use a non-locale-dependent definition of isspace() in array_in/array_out. array_in discards unquoted leading and trailing whitespace in array values, while array_out is careful to quote array elements that contain whitespace. This is problematic when the definition of "whitespace" varies between locales: array_in could drop characters that were meant to be part of the value. To avoid that, lock down "whitespace" to mean only the traditional six ASCII space characters. This change also works around a bug in OS X and some older BSD systems, in which isspace() could return true for character fragments in UTF8 locales. (There may be other places in PG where that bug could cause problems, but this is the only one complained of so far; see recent report from Steven Schlansker.) Back-patch to 9.0, but not further. Given the lack of previous reports of trouble, changing this behavior in stable branches seems to offer more risk of breaking applications than reward of avoiding problems.

Peter Eisentraut a commité :

Spell and markup checking for docs.
In pgsql/doc/src/sgml/lo.sgml, revert: looks like Binary Large OBject[sic] wasn't a misspelling
Backpatch some blatant spelling mistakes in the docs.
Remove extra newlines at end and beginning of files, add missing newlines at end of files.

Michael Meskes a commité :

Applied Zoltan Boszormenyi's patch to fix a few memleaks in ecpg's pgtypeslib.

Heikki Linnakangas a commité :

In pgsql/src/backend/parser/parse_param.c, coerce 'unknown' type parameters to the right type in the fixed-params parse_analyze() function. That case occurs e.g with PL/pgSQL EXECUTE ... USING 'stringconstant'. The coercion with a CoerceViaIO node. The result is similar to the coercion via input function performed for unknown constants in coerce_type(), except that this happens at runtime. Backpatch to 9.0. The issue is present in 8.4 as well, but the coerce param hook infrastructure this patch relies on was introduced in 9.0. Given the lack of user reports and harmlessness of the bug, it's not worth attempting a different fix just for 8.4.
Revert patch to coerce 'unknown' type parameters in the backend. As Tom Lane pointed out, it would need a 2nd pass after the whole query is processed to correctly check that an unknown Param is coerced to the same target type everywhere. Adding the 2nd pass would add a lot more code, which doesn't seem worth the risk given that there isn't much of a use case for passing unknown Params in the first place. The code would work without that check, but it might be confusing and the behavior would be different from the varparams case. Instead, just coerce all unknown params in a PL/pgSQL USING clause to text. That's simple, and is usually what users expect. Revert the patch in CVS HEAD and master, and backpatch the new solution to 8.4. Unlike the previous solution, this applies easily to 8.4 too.

Robert Haas a commité :

Tidy up a few calls to smrgextend(). In the new API introduced by my patch to include the backend ID in temprel filenames, the last argument to smrgextend() became skipFsync rather than isTemp, but these calls didn't get the memo. It's not really a problem to pass rel->rd_istemp rather than just plain false, because smgrextend() now automatically skips the fsync for temprels anyway, but this seems cleaner and saves some minute number of cycles.
In pgsql/src/backend/storage/buffer/bufmgr.c, remove the isLocalBuf argument from ReadBuffer_common. Since an SMgrRelation now knows whether or not the underlying relation is temporary, there's no point in also passing that information via an additional argument.

Magnus Hagander a commité :

Add vacuum and analyze counters to pg_stat_*_tables views.
In pgsql/src/test/regress/expected/rules.out, adjust regression tests for previous commit, that I forgot to include...

Bruce Momjian a commité :

In pgsql/doc/src/sgml/config.sgml, document that autovacuum_freeze_max_age is used for pg_clog recycling. We already mentioned xid wraparound.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

Pavel Stehule sent in two revisions of a patch to extend psql's tab completion to more entities.
KaiGai Kohei sent in a patch to implement preload libraries for single-user mode.
Peter Eisentraut sent in a prototype query progress indicator.
Quan Zongliang sent in a patch to enable pg_ctl on Windows to select a service start type (auto or on-demand), then a follow-up patch to add the docs. David Fetter unified these into standard format.
Robert Haas and Alex Hunsaker traded patches to create a new tool for git histories.
Peter Eisentraut sent in a patch to fix an issue in PL/PythonU with Python 2.7.
Heikki Linnakangas sent in a WIP patch to fix an issue with type coercion in PL/pgsql's EXECUTE ... USING construct.
Pavel Stehule sent in two revisions of a patch to add MEDIAN() and PERCENTILE() as contrib modules.
Boxuan Zhai sent in another revision of the MERGE patch.
Robert Haas sent in another refactor of comment.c.
Martin Pitt sent in a patch to add a system-wide fallback directory for SSL root certificates.
KaiGai Kohei sent in a patch to add a security hook at authorization time.
Robert Haas sent in a patch to clean up smgr, which kicked off a discussion of the design of the abstraction layers nearby.
Magnus Hagander sent in a patch to add columns the pg_stat_*_tables which record the number of [auto]vacuum and [auto]analyze runs.
Peter Eisentraut sent in a patch to refactor makeVar in the back end.
Erik Rijkers sent in two revisions of a patch to make the debug messages in pg_archivecleanup more consistent.
Magnus Hagander sent in a patch to track more vacuum stats.

Nouvelles hebdomadaires de PostgreSQL - 15 août 2010

2010-08-17T15:50:17+00:00

Les nouveautés des produits dérivés

Npgsql 2.0.10, un connecteur [ndt: data provider] .NET / PostgreSQL : http://www.npgsql.org

PostgreSQL Local

La FrOSCon 2010 aura lieu à St. Augustin (Allemagne) les 21 & 22 août 2010. Le PUG allemand a obtenu sa propre salle de dev. et est à la recherche de conférenciers. Plus de détails : http://psoos.blogspot.com/2010/08/postgresql-at-froscon-2010.html
L'appel à conférenciers pour la "West" est lancé jusqu'au 5 septembre 2010. Détails sur : http://www.postgresqlconference.org/

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.

(lien vers l'article original)

Correctifs appliqués

Tom Lane a commité :

Modify the handling of RAISE without parameters so that the error it throws can be caught in the same places that could catch an ordinary RAISE ERROR in the same location. The previous coding insisted on throwing the error from the block containing the active exception handler; which is arguably more surprising, and definitely unlike Oracle's behavior. Not back-patching, since this is a pretty obscure corner case. The risk of breaking somebody's code in a minor version update seems to outweigh any possible benefit. Piyush Newe, reviewed by David Fetter.
Fix incorrect logic in plpgsql for cleanup after evaluation of non-simple expressions. We need to deal with this when handling subscripts in an array assignment, and also when catching an exception. In an Assert-enabled build these omissions led to Assert failures, but I think in a normal build the only consequence would be short-term memory leakage; which may explain why this wasn't reported from the field long ago. Back-patch to all supported versions. 7.4 doesn't have exceptions, but otherwise these bugs go all the way back. Heikki Linnakangas and Tom Lane.
Add three-parameter forms of array_to_string and string_to_array, to allow better handling of NULL elements within the arrays. The third parameter is a string that should be used to represent a NULL element, or should be translated into a NULL element, respectively. If the third parameter is NULL it behaves the same as the two-parameter form. There are two incompatible changes in the behavior of the two-parameter form of string_to_array. First, it will return an empty (zero-element) array rather than NULL when the input string is of zero length. Second, if the field separator is NULL, the function splits the string into individual characters, rather than returning NULL as before. These two changes make this form fully compatible with the behavior of the new three-parameter form. Pavel Stehule, reviewed by Brendan Jurd.
Remove the arbitrary (and undocumented) limit on the number of parameter=value pairs that can be handled by xslt_process(). There is much else to do here, but this patch seems useful in its own right for as long as this code survives. Pavel Stehule, reviewed by Mike Fowler.
Extend psql's \e and \ef commands so that a line number can be specified, and the editor's cursor will be initially placed on that line. In \e the lines are counted with respect to the query buffer, while in \ef they are counted with line 1 = first line of function body. These choices are useful for positioning the cursor on the line of a previously-reported error. To avoid assumptions about what switch the user's editor takes for this purpose, invent a new psql variable EDITOR_LINENUMBER_SWITCH with (at present) no default value. One incompatibility from previous behavior is that "\e 1234" will now take "1234" as a line number not a file name. There are at least two ways to select a numerically-named file if you really want to. Pavel Stehule, reviewed by Jan Urbanski, with further editing by Robert Haas and Tom Lane.
Add the ability to compute per-statement latencies (ie, average execution times) to pgbench. Florian Pflug, reviewed by Greg Smith.
In pgsql/contrib/pgbench/pgbench.c, get rid of a bunch of dubious error handling code in pgbench by just erroring out immediately on any out-of-memory condition. It's rather pointless to imagine that pgbench will be able to continue usefully after a malloc failure, and in any case there were a number of unchecked mallocs.
Fix pg_restore to complain if any arguments remain after parsing the switches and input file name, per bug #5617 from Leo Shklovskii. Rearrange the corresponding code in pg_dump and pg_dumpall so that all three programs handle this in a consistent, straightforward fashion. Back-patch to 9.0, but no further. Although this is certainly a bug, it's possible that people have scripts that will be broken by the added error check, so it seems better not to change the behavior in stable branches.
Fix Assert failure in PushOverrideSearchPath when trying to restore a search path that specifies useTemp, but there is no active temp schema in the current session. (This can happen if the path was saved during a transaction that created a temp schema and was later rolled back.) For existing callers it's sufficient to ignore the useTemp flag in this case, though we might later want to offer an option to create a fresh temp schema. So far as I can tell this is just an Assert failure: in a non-assert build, the code would push a zero onto the new search path, which is useless but not very harmful. Per bug report from Heikki. Back-patch to 8.3; prior versions don't have this code.
Add xml_is_well_formed, xml_is_well_formed_document, xml_is_well_formed_content functions to the core XML code. Per discussion, the former depends on XMLOPTION while the others do not. These supersede a version previously offered by contrib/xml2. Mike Fowler, reviewed by Pavel Stehule.
Minor #include cleanup. I just noticed that libpq's pqsignal.h was violating our general inclusion style guidelines by explicitly including postgres_fe.h. Remove that, and put it in pqsignal.c where it belongs.
In pgsql/src/bin/psql/help.c, clean up failure to use ClosePager() where appropriate. Also prevent possible repeat opening of pager in helpSQL().
In pgsql/src/include/storage/backendid.h, myBackendId now needs to be PGDLLIMPORT, so that contrib modules can access it on Windows. Per buildfarm.
Add a \sf (show function) command to psql, for those times when you need to look at a function but don't wish to fire up an editor. Pavel Stehule, reviewed by Jan Urbanski
Fix \ef and \sf to not fail on functions with nonnull probin. Update comment about them in pg_get_functiondef.
In pgsql/src/backend/optimizer/util/clauses.c, fix planner to make a reasonable assumption about the amount of memory space used by array_agg(), string_agg(), and similar aggregate functions that use "internal" as their transition datatype. The previous coding thought this took *no* extra space, since "internal" is pass-by-value; but actually these aggregates typically consume a great deal of space. Per bug #5608 from Itagaki Takahiro, and fix suggestion from Hitoshi Harada. Back-patch to 8.4, where array_agg was introduced.
In pgsql/doc/src/sgml/pgbench.sgml, avoid unnecessary use of TPS acronym. Robert Haas, per gripe from Erik Rijkers.
In pgsql/doc/src/sgml/pgarchivecleanup.sgml, improve pgarchivecleanup documentation, per comments from Satoshi Nagayasu.
In pgsql/doc/src/sgml/func.sgml, clarify bit numbering in get_bit/set_bit etc. Per gripe from Zoltan Boszormenyi.
In pgsql/doc/src/sgml/backup.sgml, assorted improvements to backup/restore documentation, per Thom Brown.
In pgsql/src/bin/psql/mbprint.c, fix psql's copy of utf2ucs() to match the backend's copy exactly; in particular, propagate a fix in the test to see whether a UTF8 character has length 4 bytes. This is likely of little real-world consequence because 5-or-more-byte UTF8 sequences are not supported by Postgres nor seen anywhere in the wild, but still we may as well get it right. Problem found by Joseph Adams. Bug is aboriginal, so back-patch all the way.

Robert Haas a commité :

In the libpq docs, provide stable target anchors for libpq functions. Daniele Varrazzo.
Use double quotes rather than double quotes for libpq target anchors. Per observation from Tom Lane that the previous patch to these files was not consistent with what is done elsewhere in the docs.
In pgsql/doc/src/sgml/ecpg.sgml, fix incorrect errno definitions in ECPG manual. ecpgerrno.h hasn't materially changed since PostgreSQL 7.4, so this has been wrong for a very long time. Back-patch all the way. Satoshi Nagayasu.
In pgsql/doc/src/sgml/ecpg.sgml, fix one more incorrect errno definition in the ECPG manual. Again, back-patch all the way to 7.4.
Correct sundry errors in Hot Standby-related comments. Fujii Masao.
In pgsql/doc/src/sgml/syntax.sgml, reorder docs on lexical structure slightly for clarity. Thom Brown.
In pgsql/src/backend/access/transam/xact.c, make RecordTransactionCommit() respect wal_level. Since the only purpose of WAL-logging SharedInvalidationMessages is to support Hot Standby operation, they needn't be included when wal_level < hot_standby. Back-patch to 9.0. Review by Heikki Linnakanagas and Fujii Masao.
Include the backend ID in the relpath of temporary relations. This allows us to reliably remove all leftover temporary relation files on cluster startup without reference to system catalogs or WAL; therefore, we no longer include temporary relations in XLOG_XACT_COMMIT and XLOG_XACT_ABORT WAL records. Since these changes require including a backend ID in each SharedInvalSmgrMsg, the size of the SharedInvalidationMessage.id field has been reduced from two bytes to one, and the maximum number of connections has been reduced from INT_MAX / 4 to 223-1. It would be possible to remove these restrictions by increasing the size of SharedInvalidationMessage by 4 bytes, but right now that doesn't seem like a good trade-off. Review by Jaime Casanova and Tom Lane.
Fix assorted dtrace breakage caused by patch to include backend IDs in temp relpaths. Per buildfarm.
Further dtrace adjustments for the backend-IDs-in-relpath patch. Update the documentation, and back out a few ill-considered changes whose folly I failed to realize for failure to read the documentation.
Add doc link and additional index reference to pgcrypto. Kevin Grittner, with markup adjustments.
In pgsql/src/backend/storage/lmgr/lmgr.c, make LockDatabaseObject() AcceptInvalidationMessages(). This is appropriate for the same reasons we already do it in LockSharedObject(): things might have changed while we were waiting for the lock. There doesn't seem to be a live bug here at the moment, but that's mostly because it isn't currently used for very much.

Bruce Momjian a commité :

In pgsql/doc/src/sgml/ref/explain.sgml, add EXPLAIN documentation example. Gabrielle Roth. Backpatch to 9.0.X.
In pgsql/doc/src/sgml/syntax.sgml, properly lowercase identifiers, uppercase keywords, in doc examples.
In pgsql/doc/src/sgml/syntax.sgml, back out syntax case changes --- seems they were intentional.

Peter Eisentraut a commité :

In pgsql/doc/src/sgml/datatype.sgml, <example> is a floating element, so it's use is inappropriate when the surrounding text refers to the example inline.
Add some links to tables in the docs.

Heikki Linnakangas a commité :

In pgsql/src/backend/utils/adt/arrayfuncs.c, the sanity check added to array_recv() wa a bit too tight; we must continue to accept an empty array with dimension information. array_send() can output such arrays. Per report from Vladimir Shakhov.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

Erik Rijkers sent in a doc patch for pgbench defining TPS to mean "transactions per second."
Kris Jurka sent in another revision of the patch to fix COPY IN.
Peter Eisentraut sent in a patch to allow specifying hosts by name in pg_hba.conf.
Pavel Stehule sent in another revision of the GROUPING SETS patch.
Robert Haas sent in a patch to reduce the size of the id for SharedInvalidationMessages to one byte.
Boxuan Zhai sent in four more revisions of the MERGE patch, and Heikki Linnakangas responded with a cleaned-up one.
Joseph Adams sent in two more WIP patches to add the JSON type, the second adding it as a core type rather than the previous contrib.
Fujii Masao sent in a patch to align the docs and code for trace_recovery_messages.
Greg Smith sent in another revision of the patch to add individual statement latencies to pgbench.
Joseph Adams sent in a patch to fix utf8-to-unicode.
Joseph Adams sent in some general utility functions for, among other things, enum handling in C stored procedures.
Zoltan Boszormenyi sent in a WIP patch to add replication to the SQL syntax.
Dean Rasheed sent in another WIP patch to implement triggers on views.
Robert Haas sent in another revision of the patch to refactor comment.c.

Traduction disponible pour PostgreSQL 9.0 beta 4

2010-08-16T19:27:00+00:00

J'ai mis du temps à m'y coller mais c'est enfin fait. Le merge a été réalisé samedi soir et les quelques paragraphes à traduire ont été traités dimanche matin. Dans l'ensemble, ça a été plutôt rapide.

Du coup, j'en ai profité pour travailler à la génération d'un format CHM. On l'avait proposé pendant un certain temps et je ne sais plus trop pourquoi, on l'avait supprimé. Bref. J'ai fait le nécessaire pour que ce format soit de nouveau disponible. Attention, cela ne concerne que les versions 8.1 à 9.0. Les versions 7.4 et 8.0 n'en bénéficieront pas, étant donné qu'elles n'auront plus qu'une version corrective avant d'être complètement oubliées pour les correctifs.

J'ai profité de we week-end pour mettre à jour la traduction du manuel de Slony. Nous ne disposions toujours que de la 2.0.3. Le manuel français de la 2.0.4 est enfin disponible. Le site web français a aussi été mis à jour.

Nouvelles hebdomadaires de PostgreSQL - 8 août 2010

2010-08-10T21:50:45+00:00

Visite guidée de PostgreSQL 9.0 par Bruce Momjian lors du prochain "NYC PostgreSQL Meetup", le 10 août à 18h. RSVP ci-après : http://www.meetup.com/postgresql-3/calendar/14310923/

Les nouveautés des produits dérivés

Npgsql 2.0.10, un "fournisseur de données" PostgreSQL pour .NET : http://www.npgsql.org

Offres d'emplois autour de PostgreSQL en août

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

PostgreSQL Local

La FrOSCon 2010 aura lieu à St. Augustin (Allemagne) les 21 & 22 août 2010. Le PUG allemand a obtenu sa propre salle de dev. et est à la recherche de conférenciers. Plus de détails : http://andreas.scherbaum.la/blog/archives/711-FrOSCon-2010-PostgreSQL-devroom-Call-for-papers.html
L'appel à conférenciers pour la "West" est lancé jusqu'au 5 septembre 2010. Détails sur : http://www.postgresqlconference.org/

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.

(lien vers l'article original)

Revues

Brendan Jurd reviewed the patch to reduce the on-disk size of NUMERIC.

KaiGai Kohei reviewed Robert Haas's patch to refactor comment.c

Correctifs appliqués

Simon Riggs a commité :

Reduce lock levels of CREATE TRIGGER and some ALTER TABLE, CREATE RULE actions. Avoid hard-coding lockmode used for many altering DDL commands, allowing easier future changes of lock levels. Implementation of initial analysis on DDL sub-commands, so that many lock levels are now at ShareUpdateExclusiveLock or ShareRowExclusiveLock, allowing certain DDL not to block reads/writes. First of number of planned changes in this area; additional docs required when full project complete.

Robert Haas a commité :

Remove ancient PL/pgsql line numbering hack. While this hack arguably has some benefit in terms of making PL/pgsql's line numbering match the programmer's expectations, it also makes PL/pgsql inconsistent with the remaining PLs, making it difficult for clients to reliably determine where the error actually is. On balance, it seems better to be consistent. Pavel Stehule
Add btree_gist support for searching on "not equals". Jeff Davis, with slight editorialization by me.
In contrib/fuzzystrmatch, teach levenshtein() about multi-byte characters. Based on a patch by, and further ideas from, Alexander Korotkov.
In pgsql/src/backend/commands/tablecmds.c, fix inheritance count tracking in ALTER TABLE .. ADD CONSTRAINT. Without this patch, constraints inherited by children of a parent table which itself has multiple inheritance parents can end up with the wrong coninhcount. After dropping the constraint, the children end up with a leftover copy of the constraint that is not dumped and cannot be dropped. There is a similar problem with ALTER TABLE .. ADD COLUMN, but that looks significantly more difficult to resolve, so I'm committing this fix separately. Back-patch to 8.4, which is the first release that has coninhcount. Report by Hank Enting.
Regression tests for new btree_gist "not equals" support. Jeff Davis, with minor adjustments by me.
In pgsql/src/backend/utils/adt/numeric.c, allow numeric to use a more compact, 2-byte header in many cases. Review by Brendan Jurd and Tom Lane.
In pgsql/src/backend/utils/adt/numeric.c, fix numeric_maximum_size() calculation. The old computation can sometimes underestimate the necessary space by 2 bytes; however we're not back-patching this, because this result isn't used for anything critical. Per discussion with Tom Lane, make the typmod test in this function match the ones in numeric() and apply_typmod() exactly.
In pgsql/src/include/utils/numeric.h, fix declared argument name for numeric_maximum_size. The previous commit changed the function to say 'typmod' rather than 'typemod', but I forgot to update the header file.
Standardize get_whatever_oid functions for object types with unqualified names: 1. Add a missing_ok parameter to get_tablespace_oid. 2. Avoid duplicating get_tablespace_od guts in objectNamesToOids. 3. Add a missing_ok parameter to get_database_oid. 4. Replace get_roleid and get_role_checked with get_role_oid. 5. Add get_namespace_oid, get_language_oid, get_am_oid. 6. Refactor existing code to use new interfaces. Thanks to KaiGai Kohei for the review.
Standardize get_whatever_oid functions for other object types: 1. Rename TSParserGetPrsid to get_ts_parser_oid. 2. Rename TSDictionaryGetDictid to get_ts_dict_oid. 3. Rename TSTemplateGetTmplid to get_ts_template_oid. 4. Rename TSConfigGetCfgid to get_ts_config_oid. 5. Rename FindConversionByName to get_conversion_oid. 6. Rename GetConstraintName to get_constraint_oid. 7. Add new functions get_opclass_oid, get_opfamily_oid, get_rewrite_oid, get_rewrite_oid_without_relid, get_trigger_oid, and get_cast_oid. The name of each function matches the corresponding catalog. Thanks to KaiGai Kohei for the review.
In pgsql/src/backend/utils/cache/syscache.c, fix incorrect pathname in comment.
In pgsql/doc/src/sgml/release-9.0.sgml, rearrange "big features" section of the release notes. Josh Berkus

Tom Lane a commité :

Fix core dump in QTNodeCompare when tsquery_cmp() is applied to two empty tsqueries. CompareTSQ has to have a guard for the case rather than blindly applying QTNodeCompare to random data past the end of the datums. Also, change QTNodeCompare to be a little less trusting: use an actual test rather than just Assert'ing that the input is sane. Problem encountered while investigating another issue (I saw a core dump in autoanalyze on a table containing multiple empty tsquery values). Back-patch to all branches with tsquery support. In HEAD, also fix some bizarre (though not outright wrong) coding in tsq_mcontains().
Be a little more careful with the shift computations in QT2QTN and makeTSQuerySign. The first of these is a live bug, on some platforms, as per bug #5590 from John Regehr. However the consequences seem limited because of the relatively narrow scope of use of QTNode.sign. The shift in makeTSQuerySign is actually safe because TSQS_SIGLEN is unsigned, but it seems like a good idea to insert an explicit cast rather than depend on that.
In pgsql/doc/src/sgml/btree-gist.sgml, fix markup, other minor editing for recent btree_gist doc changes.
In pgsql/src/backend/utils/adt/nabstime.c, add some comments to tinterval_cmp_internal pointing out its severe implementation deficiencies. Per discussion of bug #5592, we're not going to change it, but these things should be documented so that if anyone ever reimplements type tinterval, they will be more careful.
Kibitzing on \conninfo patch: adjust the order of field output to match the parameters of \connect, and fix oversight of not enabling translation of the messages. Also, adjust \connect's similar messages to match, and deal with 8.2-era violation of basic translatability guidelines there.
In pgsql/doc/src/sgml/config.sgml, fix mangled grammar.
Code review for --quote-all-identifiers patch: add missing --help documentation for new pg_dump/pg_dumpall parameters, make a couple of trivial stylistic adjustments to make the code follow usual project style.
Replace the naive HYPOT() macro with a standards-conformant hypotenuse function. This avoids unnecessary overflows and probably gives a more accurate result as well. Paul Matthews, reviewed by Andrew Geery
In pgsql/doc/src/sgml/syntax.sgml, add an example to clarify the use of ORDER BY in multiple-argument aggregates. People seem to not get this right without help.
In pgsql/doc/src/sgml/libpq.sgml, fix sloppy mistakes in documentation of PQescapeLiteral and PQescapeIdentifier. Noted by Dmitriy Igrishin.
In pgsql/doc/src/sgml/syntax.sgml, forgot to back-patch earlier change to documentation for aggregate ORDER BY clauses. Tags: ---- REL9_0_STABLE
Remove the single-argument form of string_agg(). It added nothing much in functionality, while creating an ambiguity in usage with ORDER BY that at least two people have already gotten seriously confused by. Also, add an opr_sanity test to check that we don't in future violate the newly minted policy of not having built-in aggregates with the same name and different numbers of parameters. Per discussion of a complaint from Thom Brown.
In pgsql/src/backend/parser/parse_func.c, add a very specific hint for the case that we're unable to locate a function matching a call like f(x, ORDER BY y,z). It could be that what the user really wants is f(x,z ORDER BY y). We now have pretty conclusive evidence that many people won't understand this problem without concrete guidance, so give it to them. Per further discussion of the string_agg() problem.
In pgsql/src/backend/utils/misc/guc.c, add a comment about the initial default value of max_stack_depth.
In pgsql/doc/src/sgml/release-9.0.sgml, fix inaccurate description of deferrable unique constraints, per Dean Rasheed.
In pgsql/doc/src/sgml/release-9.0.sgml, let's put that </link> in a sane place ...
Recognize functional dependency on primary keys. This allows a table's other columns to be referenced without listing them in GROUP BY, so long as the primary key column(s) are listed in GROUP BY. Eventually we should also allow functional dependency on a UNIQUE constraint when the columns are marked NOT NULL, but that has to wait until NOT NULL constraints are represented in pg_constraint, because we need to have pg_constraint OIDs for all the conditions needed to ensure functional dependency. Peter Eisentraut, reviewed by Alex Hunsaker and Tom Lane.
Add stats functions and views to provide access to a transaction's own statistics counts. These numbers are being accumulated but haven't yet been transmitted to the collector (and won't be, until the transaction ends). For some purposes, though, it's handy to be able to look at them. Joel Jacobson, reviewed by Itagaki Takahiro
Add an xpath_exists() function. This is equivalent to XMLEXISTS except that it offers support for namespace mapping. Mike Fowler, reviewed by David Fetter

Bruce Momjian a commité :

In pgsql/doc/src/sgml/ref/explain.sgml, add EXPLAIN documentation example. Gabrielle Roth.
In pgsql/doc/src/sgml/release-9.0.sgml, fix 9.0 release notes vacuum mention, not -> now. Peter Fokkinga.

Peter Eisentraut a commité :

Add xmlexists function by Mike Fowler, reviewed by Peter Eisentraut.
In pgsql/doc/src/sgml/plpython.sgml, document which Python environment variables affect PL/Python
In pgsql/doc/src/sgml/xfunc.sgml, fix indexterm spelling.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

Mike Fowler sent in another revision of the xml_is_well_formed() patch.
Robert Haas and Yeb Havinga traded patches fixing the issue with multiply-inherited columns.
Tom Lane sent in a patch to fix an issue with ANALYZE in the case of expression indexes with opckeytype that is not the default one.
Pavel Stehule and Robert Haas traded patches for the \ef [line number] and \sf (show function) feature in psql.
Zoltan Boszormenyi sent in another revision of the lock_timeout patch.
Pavel Stehule sent in two more revisions of the xslt with no limits patch.
Josh Tolley, David Fetter and Pavel Stehule sent in new revisions of the GROUPING SETS patch.
Florian Pflug sent in another revision of the "true serialization" patch.
Zoltan Boszormenyi sent in a patch to fix ECPG in the case of dynamic cursor names, which did not exist before 9.0.
Florian Pflug sent in two more revisions of the patch to show individual statement latencies in pgbench output.
Boxuan Zhai, Heikki Linnakangas and Simon Riggs traded patches which implement, describe and test MERGE.
Simon Riggs sent in a detailed specification for MERGE.
Dean Rasheed sent in a WIP patch to add triggers for VIEWs.
Jan Otto sent in a patch to fix and update contrib/isn.
Fujii Masao sent in another patch to help with synchronous replication.
Heikki Linnakangas sent in a patch to fix an infelicity in EXECUTE ... USING with unknown parameters.
Robert Haas sent in a patch to refactor comment.c, partly as a preface to adding a SECURITY LABEL command.
Tom Lane sent in another revision of the gincostestimate patch.
Kris Jurka sent in another revision of the patch to fix JDBC in certain situations with COPY IN.
Tom Lane sent in a patch with a different approach to the gincostestimate issue.
Peter Eisentraut sent in a patch to add the following functionalities to ALTER TYPE: ADD ATTRIBUTE, DROP ATTRIBUTE, ALTER ATTRIBUTE...SET DATA TYPE and RENAME ATTRIBUTE.
Mark Wong sent in a WIP patch to implement parallel quicksort.

Des news de pgpool-II v.3.0

2010-08-06T14:00:00+00:00

Tatsuo Ishii, développeur principal de pgpool-II, vient d'annoncer ce matin, dans la liste dédiée aux développeurs de pgpool-II, que la première version beta de pgpool-II en version 3.0 sortirait ce mois-ci.

Il a donné aussi une liste des fonctionalités que cette version apporte dans le même mail.

Je vous en propose ci-après une traduction libre.

Version 3.0(umiyameboshi) 2010/08/xx:

Ceci est la première version de pgpool-II dans la branche 3.0. Il s'agit d'un grand bond en avant depuis les versions 2.2 ou 2.3.

La grosse nouveauté avec cette nouvelle version est qu'elle est adaptée à la nouvelle version 9.0 de PostgreSQL (NDT: sortie prévue pour l'automne 2010), et en particulier à ses fonctionalités de Streaming Replication/Hot Standby.

Le Streaming Replication peut être utilisé dans le mode "master/slave" de pgpool-II. Ce mode maître/esclave de pgpool-II lui-même a été grandement amélioré:

les SELECTs dans des transactions explicites peuvent être balancés

dans le protocole étendu, les mesages PARSE/BIND/DESCRIBE sont envoyés au nœud qui exécute le message EXECUTE. Cela réduit la contention au niveau des locks

l'auto-start d'une transaction se produit désormais uniquement si c'est nécessaire

les tables temporaires peuvent être utilisées sans risques désormais

les SELECTs qui appellent des fonctions qui peuvent potentiellement déclencher des écritures ne s'exécutent que sur le maître (master, primary)

D'autres nouvelles fonctionalités sont ajoutées grâce à un recodage du cœur de pgpool-II. Par exemple, dans le mode réplication, les SELECTs qui appellent des fonctions qui peuvent potentiellement déclencher des écritures ne pourront pas être balancés. Nouvelles fonctionalités (NDT: on trouve entre parenthèse le nom du codeur qui a pris en charge la fonctionalité, presque toujours Tatsuo)

le Online recovery peut être utilisé même dans le mode maître/esclave en mode streaming replication (Tatsuo)

la nouvelle directive "delay_threshold" a été ajoutée pour monitorer le décalage de la réplication dans le mode maître/esclave avec streaming replication. Si ce décalage devient trop important (NDT: supérieur à la valeur de "delay_threshold"), alors les SELECTs ne sont plus balancés (Tatsuo)

la commande "show pool_status" montre le décalage de la réplication en mode maître/esclave avec streaming replication (Tatsuo)

la nouvelle directive "log_standby_delay" a été ajoutée pour tracer le décalage de la réplication en mode master/slave avec streaming replication (Tatsuo)

le numéro de processus du backend a été ajouté aux informations de pcp_proc_info, que le client se connecte ou non au pool (Tatsuo)

les nouvelles directives "white_function_list" et "black_function_list" ont été ajoutées pour déclarer les fonctions qui sont suceptibles de provoquer des écritures ou pas (Tatsuo) (NDT: c'est ainsi que pgpool peut distinguer les fonctions qui peuvent provoquer des écritures des autres. Il n'y a donc pas de magie!)

dans mode de réplication maître/esclave, les SELECTs sur des tables temporaires ne s'exécutent que sur maître/primaire (Tatsuo)

dans le mode de réplication maître/esclave, les requêtes d'écritures se trouvant en dehors d'une transaction explicite ne déclenchent plus de trasactions internes (Tatsuo)

dans le mode de réplication maître/esclave, les SELECTs à l'intérieur d'une transaction sont load-balancés (Tatsuo, Kitawaga)

dans le mode de réplication maître/esclave, les commandes ne sont pas envoyées à tous les serveurs. Cela permettra d'éviter des locks superflus (Tatsuo, Kitawaga)

une nouvelle option de démarrage de pgpool-II permet d'ignorer le fichier de statut (Tatsuo) (NDT: précédement, si ce fichier était présent, dans certains cas particuliers, pgpool ne pouvait plus démarrer, sauf à supprimer ce fichier)

support de la nouvelle syntaxe du VACUUM introduite dans la version 9.0 de PostgreSQL (Tatsuo)

la nouvelle directive "failover_if_affected_tuples_mismatch" permet de contrôler le comportement de pgpool-II lorsque le nombre d'enregistrements affectés ou renvoyés par une requête de type INSERT, UPDATE ou DELETE diffère (Tatsuo)

lorsque le nombre de ces enregistrements diffère sur un INSERT, UPDATE ou DELETE, ce dernier est tracé, pour chacun des serveurs impactés (Tatsuo)

l'authentification md5 est supportée dans le mode réplication ainsi que dans le mode maître/esclave (Tatsuo)

on peut désormais forcer le passage à la deuxième étape du mode online recovery, même lorsqu'il y a des clients connectés (Tatsuo)

s'il y a seulement un seul serveur de disponible et que ce dernier a une avarie (pgpool-II provoque alors un failover), pgpool-II se connectera automatiquement à ce dernier dès qu'il sera à nouveau disponible (Tatsuo)

ajout du format des options longues à PCP (Guillaume Lelarge)

la nouvelle directive "debug_level" permet de contrôler le niveau des traces de débogage dans les fichiers de log

on peut désormais utiliser plusieurs représentations pour les valeurs booléennes dans le fichier pgpool.conf (Kitawaga)

Corrections de bugs

Un bug de gestion des timeouts a été corrigé dans les commandes PCP (Tatsuo)

le blocage de SSL lorsque de grosses quantités de données sont transférées a été corrigé (Tatsuo)

le failover lorsqu'il n'y a plus qu'un seul serveur de disponible a été corrigé (Tatsuo)

Nouvelles hebdomadaires de PostgreSQL - 1er août 2010

2010-08-03T23:46:10+00:00

PostgreSQL 9.0 beta 4 est disponible. Testez ! [ndt: annonce (fr)] http://www.postgresql.org/developer/beta

Job::Machine 0.011, un gestionnaire de queue en Perl utilisant PostgreSQL : http://search.cpan.org/dist/Job-Machine/

pgAdmin 1.10.5, une interface graphique de gestion pour PostgreSQL : http://www.pgadmin.org/download/

pg_sample 0.01, un utilitaire permettant d'exporter un petit échantillon d'une base de données : http://github.com/mla/pg_sample

Offres d'emplois autour de PostgreSQL en août

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

PostgreSQL Local

Reuven Lerner donnera un cours de 5 jours sur PostgreSQL du 1er au 5 août au "Hi-Tech College" de Herzliya (Israël) : http://www.hi-tech.co.il/college/default.asp?PageID=12&CourseNum=4288
La FrOSCon 2010 aura lieu à St. Augustin (Allemagne) les 21 & 22 août 2010. Le PUG allemand a obtenu sa propre salle de dev. et est à la recherche de conférenciers. Plus de détails : http://andreas.scherbaum.la/blog/archives/711-FrOSCon-2010-PostgreSQL-devroom-Call-for-papers.html
L'appel à conférenciers pour la "West" est lancé jusqu'au 5 septembre 2010. Détails sur : http://www.postgresqlconference.org/

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.

(lien vers l'article original)

Revues

KaiGai Kohei reviewed Robert Haas's patch to add get_whatever_oid functionality.

Correctifs appliqués

Peter Eisentraut a commité :

In pgsql/doc/src/sgml/xfunc.sgml, add table creation and population to example. From John Gage.
In pgsql/doc/src/sgml/perform.sgml, fix grammar. Backpatched to 8.1.
In pgsql/contrib/xml2/README.xml2, spelling fix.
Spelling fixes.
In pgsql/src/bin/psql/common.c, show psql timing output even in quiet mode. These two settings ought to be independent of each other.
In pgsql/contrib/chkpass/chkpass.sql.in, remove wildly obsolete type attribute externallength from chkpass.
Fix indentation of verbatim block elements. Block elements with verbatim formatting (literallayout, programlisting, screen, synopsis) should be aligned at column 0 independent of the surrounding SGML, because whitespace is significant, and indenting them creates erratic whitespace in the output. The CSS stylesheets already take care of indenting the output. Assorted markup improvements to go along with it.
Translation updates for 9.0beta4.

Alvaro Herrera a commité :

In PL/Perl[U], ensure $_SHARED is declared in the main:: namespace, per bugs #5570 and #5571. Author: Alex Hunsaker

Robert Haas a commité :

In postgresql.conf.sample, use on/off rather than true/false. We used to be consistent about this, but my recent patch to add a restart_after_crash GUC failed to follow the existing convention. Report and patch from Fujii Masao.
In pgsql/doc/src/sgml/plpgsql.sgml, fix typo in PL/pgsql code example. Backpatch to 8.4. Marc Cousin. Review by Kevin Grittner.
Add ssl_cipher() and ssl_version() functions to contrib/sslinfo. Review by Dave Page.
In pgsql/src/backend/access/heap/heapam.c, fix possible page corruption by ALTER TABLE .. SET TABLESPACE. If a zeroed page is present in the heap, ALTER TABLE .. SET TABLESPACE will set the LSN and TLI while copying it, which is wrong, and heap_xlog_newpage() will do the same thing during replay, so the corruption propagates to any standby. Note, however, that the bug can't be demonstrated unless archiving is enabled, since in that case we skip WAL logging altogether, and the LSN/TLI are not set. Back-patch to 8.0; prior releases do not have tablespaces. Analysis and patch by Jeff Davis. Adjustments for back-branches and minor wordsmithing by me.
In pgsql/contrib/fuzzystrmatch/fuzzystrmatch.c, avoid using text_to_cstring() in levenshtein functions. Operating directly on the underlying varlena saves palloc and memcpy overhead, which testing shows to be significant. Extracted from a larger patch by Alexander Korotkov.
Make details of the Numeric representation private to numeric.c. Review by Tom Lane.
Make psql distinguish between unique indices and unique constraints. Josh Kupershmidt. Reviewing and kibitzing by Kevin Grittner and me.

Tom Lane a commité :

Rewrite the rbtree routines so that an RBNode is the first field of the struct representing a tree entry, rather than being a separately allocated piece of storage. This API is at least as clean as the old one (if not more so --- there were some bizarre choices in there) and it permits a very substantial memory savings, on the order of 2X in ginbulk.c's usage.
Fix an additional set of problems in GIN's handling of lossy page pointers. Although the key-combining code claimed to work correctly if its input contained both lossy and exact pointers for a single page in a single TID stream, in fact this did not work, and could not work without pretty fundamental redesign. Modify keyGetItem so that it will not return such a stream, by handling lossy-pointer cases a bit more explicitly than we did before. Per followup investigation of a gripe from Artur Dabrowski. An example of a query that failed given his data set is select count(*) from search_tab where (to_tsvector('german', keywords ) @@ to_tsquery('german', 'ee:* | dd:*')) and (to_tsvector('german', keywords ) @@ to_tsquery('german', 'aa:*')); Back-patch to 8.4 where the lossy pointer code was introduced.
In pgsql/src/backend/tsearch/ts_selfuncs.c, add some knowledge about prefix matches to tsmatchsel(). It's not terribly bright, but it beats assuming that a prefix match behaves identically to an exact match, which is what the code was doing before :-(. Noted while experimenting with Artur Dobrowski's example.
Fix ANALYZE's ancient deficiency of not trying to collect stats for expression indexes when the index column type (the opclass opckeytype) is different from the expression's datatype. When coded, this limitation wasn't worth worrying about because we had no intelligence to speak of in stats collection for the datatypes used by such opclasses. However, now that there's non-toy estimation capability for tsvector queries, it amounts to a bug that ANALYZE fails to do this. The fix changes struct VacAttrStats, and therefore constitutes an API break for custom typanalyze functions. Therefore we can't back-patch it into released branches, but it was agreed that 9.0 isn't yet frozen hard enough to make such a change unacceptable. Ergo, back-patch to 9.0 but no further. The API break had better be mentioned in 9.0 release notes.
Back-patch fix for renaming asyncCommitLSN to asyncXactLSN. AIUI this was supposed to go into 9.0 as well as HEAD.
Fix an ancient typo that prevented the detection of conflicting fields when interval input "invalid" was specified together with other fields. Spotted by Neil Conway with the help of a clang warning. Although this has been wrong since the interval code was written more than 10 years ago, it doesn't affect anything beyond which error message you get for a wrong input, so not worth back-patching very far.
Tweak a couple of macros in the regex code to suppress compiler warnings from "clang". The VERR changes make an assignment unconditional, which is probably easier to read/understand anyway, and one can hardly argue that it's worth shaving cycles off the case of reporting another error when one has already been detected. The INSIST change limits where that macro can be used, but not in a way that creates a problem for any existing call.
In pgsql/src/template/darwin, don't try to force use of -no-cpp-precomp on OS X. It's been five years since Apple shipped a compiler that needed this switch, and there's increasing interest in using other compilers that won't accept the switch at all. Better to let anybody who still needs the switch inject it via CPPFLAGS. Per gripe from Neil Conway.
Also, fix minor memory leaks in code called by ginEntryInsert, in particular in ginInsertValue and entryFillRoot, as well as ginEntryInsert itself. These leaks resulted in the GIN index build context continuing to bloat even after we'd filled it to maintenance_work_mem and started to dump data out to the index. In combination these fixes restore the GIN index build code to honoring the maintenance_work_mem limit about as well as it did in 8.4. Speed seems on par with 8.4 too, maybe even a bit faster, for a non-pathological case in which HEAD was formerly slower. Back-patch to 9.0 so we don't have a performance regression from 8.4.
Fix potential failure when hashing the output of a subplan that produces a pass-by-reference datatype with a nontrivial projection step. We were using the same memory context for the projection operation as for the temporary context used by the hashtable routines in execGrouping.c. However, the hashtable routines feel free to reset their temp context at any time, which'd lead to destroying input data that was still needed. Report and diagnosis by Tao Ma. Back-patch to 8.1, where the problem was introduced by the changes that allowed us to work with "virtual" tuples instead of materializing intermediate tuple values everywhere. The earlier code looks quite similar, but it doesn't suffer the problem because the data gets copied into another context as a result of having to materialize ExecProject's output tuple.
In pgsql/src/backend/executor/nodeLockRows.c, fix oversight in new EvalPlanQual logic: the second loop over the ExecRowMark list in ExecLockRows() forgot to allow for the possibility that some of the rowmarks are for child tables that aren't relevant to the current row. Per report from Kenichiro Tanaka.
In pgsql/doc/src/sgml/installation.sgml, work around a documentation toolchain problem by replacing the "AIX-fixlevels" table with a <variablelist> carrying the same information. Previously the 9.0 documentation was failing to build as a US-size PDF file. It's quite obscure what the real problem is or why this avoids it, but we need a hack now so we can build docs for beta4. In passing do a bit of editing in the AIX installation docs, in particular remove a long-obsolete claim that the regression tests are likely to fail.
In pgsql/src/backend/commands/tablecmds.c, fix another longstanding problem in copy_relation_data: it was blithely assuming that a local char[] array would be aligned on at least a word boundary. There are architectures on which that is pretty much guaranteed to NOT be the case ... and those arches also don't like non-aligned memory accesses, meaning that log_newpage() would crash if it ever got invoked. Even on Intel-ish machines there's a potential for a large performance penalty from doing I/O to an inadequately aligned buffer. So palloc it instead. Backpatch to 8.0 --- 7.4 doesn't have this code.
In pgsql/src/include/catalog/pg_proc.h, clean up some inconsistencies in the volatility marking of various I/O related functions. Per today's discussion, we will henceforth assume that datatype I/O functions are either stable or immutable, never volatile. (This implies in particular that domain CHECK constraint expressions shouldn't be volatile, since domain_in executes them.) In turn, functions that execute the I/O functions of arbitrary datatypes should always be labeled stable. This affects the labeling of array_to_string, which was unsafely marked immutable, and record_in, record_out, record_recv, record_send, domain_in, domain_recv, which were over-conservatively marked volatile. The array I/O functions were already marked stable, which is correct per this policy but would have been wrong if we maintained domain_in as volatile. Back-patch to 9.0, along with an earlier fix to correctly mark cash_in and cash_out as stable not immutable (since they depend on lc_monetary). No catversion bump --- the implications of this are not currently severe enough to justify a forced initdb.
In pgsql/doc/src/sgml/release-9.0.sgml, update release notes for 9.0 beta 4. Back-patch some changes that were made only in HEAD.
Improved version of patch to protect pg_get_expr() against misuse: look through join alias Vars to avoid breaking join queries, and move the test to someplace where it will catch more possible ways of calling a function. We still ought to throw away the whole thing in favor of a data-type-based solution, but that's not feasible in the back branches. This needs to be back-patched further than 9.0, but I don't have time to do so today. Committing now so that the fix gets into 9.0beta4.
Rewrite the key-combination logic in GIN's keyGetItem() and scanGetItem() routines to make them behave better in the presence of "lossy" index pointers. The previous coding was outright incorrect for some cases, as recently reported by Artur Dabrowski: scanGetItem would fail to return index entries in cases where one index key had multiple exact pointers on the same page as another key had a lossy pointer. Also, keyGetItem was extremely inefficient for cases where a single index key generates multiple "entry" streams, such as an @@ operator with a multiple-clause tsquery. The presence of a lossy page pointer in any one stream defeated its ability to use the opclass consistentFn, resulting in probing many heap pages that didn't really need to be visited. In Artur's example case, a query like WHERE tsvector @@ to_tsquery('a & b') was about 50X slower than the theoretically equivalent WHERE tsvector @@ to_tsquery('a') AND tsvector @@ to_tsquery('b') The way that I chose to fix this was to have GIN call the consistentFn twice with both TRUE and FALSE values for the in-doubt entry stream, returning a hit if either call produces TRUE, but not if they both return FALSE. The code handles this for the case of a single in-doubt entry stream, but punts (falling back to the stupid behavior) if there's more than one lossy reference to the same page. The idea could be scaled up to deal with multiple lossy references, but I think that would probably be wasted complexity. At least to judge by Artur's example, such cases don't occur often enough to be worth trying to optimize. Back-patch to 8.4. 8.3 did not have lossy GIN index pointers, so not subject to these problems.
In pgsql/src/backend/tsearch/ts_selfuncs.c, tweak tsmatchsel() so that it examines the structure of the tsquery whenever possible (ie, whenever the tsquery is a constant), even when no statistics are available for the tsvector. For example, foo @@ 'a & b'::tsquery can be expected to be more selective than foo @@ 'a'::tsquery, whether or not we know anything about foo. We use DEFAULT_TS_MATCH_SEL as the assumed selectivity of individual query terms when no stats are available, then combine the terms according to the query's AND/OR structure as usual. Per experimentation with Artur Dabrowski's example. (The fact that there are no stats available in that example is a problem in itself, but nonetheless tsmatchsel should be smarter about the case.) Back-patch to 8.4 to keep all versions of tsmatchsel() in sync.

Simon Riggs a commité :

Add explicit regression tests for ALTER TABLE lock levels. Use this to catch a couple of lock level assignments that slipped through manual testing, per Peter Eisentraut.
Rename asyncCommitLSN to asyncXactLSN to reflect changed role in 9.0. Transaction aborts now record their LSN to avoid corner case behaviour in Streaming Replication/Hot Standby, hence change of name of variables and functions. As pointed out by Fujii Masao. Cosmetic changes only.

Marc Fournier a commité :

Tag for beta4.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

Robert Haas sent in a patch to add ssl_version() and ssl_cipher() to contrib/sslinfo.
KaiGai Kohei sent in two more patches implementing SECURITY LABEL.
Boxuan Zhai sent in two more revisions of the WIP patch for MERGE.
Alexander Korotkov sent in two more revisions of the patch to make levenshtein multibyte-aware in contrib/fuzzystrmatch.
Fujii Masao sent in another revision of the patch to do synchronous replication.
Simon Riggs sent in another patch to reduce the needed locking for ALTER TABLE.
Florian Pflug sent in another revision of the patch to show individual statement latencies in pgbench output.
Erik Rijkers sent in a patch to fix an oversight in the variadic function docs.
Robert Haas sent in another revision of the patch to reduce the on-disk size of NUMERICs.
Zoltan Boszormenyi sent in another WIP patch to add a lock_timeout GUC.
Henk Enting sent in a patch to help with the intersection of CHECK constraints and multiple inheritance.

PostgreSQL 9.0 Beta 4 disponible

2010-08-03T08:11:27+00:00

Billet original de Selena Deckelmann, corrigé par Josh Berkus. Traductions de Stéphane Schildknecht.

La quatrième version bêta de PostgreSQL 9.0 est désormais disponible. Elle contient divers correctifs et quelques changements par rapport à la bêta 3.

Plus elle sera téléchargée, installée, et testée, plus nous nous rapprocherons de la version 9.0 finale. Il est d'ailleurs fort probable qu'il s'agisse de la dernière version bêta.

Quelques modifications significatives ont été introduites dans la bêta 4 qui requièrent que les applications soient re-testées au regard de la version 9.0.

Le changement le plus significatif pour l'utilisateur concerne la remontée d'informations par \timing, même lorsque psql tourne en mode "quiet" (silencieux). Ces modifications incluent :

une remontée correcte des erreurs d'espace disque et le non-chargement

du .psqlrc lors de l'utilisation de pg_upgrade;

une vérification compète du certificat SSL lorsque « host » et « hostaddr »

sont tous deux précisés, rétro-correctif en 8.4 ;

un correctif pour la gestion des objets SQL/MED par pg_dump ;
un correctif et amélioration des performances pour le parcours de pointeurs d'index GIN à trous ;
un correctif pour une possible corruption de page dans ALTER TABLE .. SET TABLESPACE ;
la ré-exécution correcte de CREATE TABLESPACE lors d'une récupération après incident ;
le nettoyage des sous-transactions dans les boucles FOR, et la limitation des niveaux de

récursions lors de l'assignation des XID sur des niveaux multiples de sous-transactions, tous deux rétro-corrigés en 8.0.

À l'inverse des versions bêta précédentes, il n'y a pas eu de modification du catalogue système par rapport à la bêta3. initdb n'est donc pas nécessaire pour une mise à jour de la bêta3. En revanche, une mise à jour depuis des versions bêta plus anciennes nécessite un initdb et un rechargement de la base.

Nous vous encourageons à utiliser cette opportunité pour tester pg_upgrade pour les mises à jour à partir d'une version bêta plus ancienne de la version 9.0. Merci de remonter vos résultats.

Si vous pouvez nous aider à tester la version bêta, jetez un œil à la page : http://wiki.postgresql.org/wiki/HowToBetaTest

Les bêtas ne sont pas stable, et ne doivent, par conséquent, jamais être utilisées en environnement de production ; elles n'ont d'autre but que d'être testées. Une version « release candidate » sera bientôt disponible.

Le code source et les installeurs binaires pour de nombreuses plateformes sont disponibles sur le site de PostgreSQL :

Source: http://www.postgresql.org/ftp/source/v9.0beta4
One-Click installer dont version Windows 64bits :

http://www.enterprisedb.com/products/pgdownload.do

binaires pour les autres plateformes : http://www.postgresql.org/ftp/binary/v9.0beta4
Notes de version :

http://developer.postgresql.org/pgdocs/postgres/release-9-0.html

Participer aux tests : http://www.postgresql.org/developer/beta

Nouvelles hebdomadaires de PostgreSQL - 25 juillet 2010

2010-07-29T19:25:20+00:00

Les nouveautés des produits dérivés

Another PostgreSQL Diff Tool 2.0 Beta 2, un outil de "diff" pour base de données : https://sourceforge.net/apps/mediawiki/apgdiff/
JASPA 0.1RC1, un SIG en Java utilisable avec PostgreSQL : http://forge.osor.eu/projects/jaspa/
MyJSQLView 3.22, un utilitaire graphique utilisable avec PostgreSQL : http://dandymadeproductions.com/projects/MyJSQLView/index.html
Simpycity 0.3.1, un système de "mapping" [ndt: correspondance objet-BDD ?] pour Python et PostgreSQL : http://www.commandprompt.com/blogs/aurynn_shaw/2010/07/announcement_simpycity_031_released/
tail_n_mail 1.15.0, un programme en Perl pour scanner les fichiers de log et envoyer les résultats par mail : http://bucardo.org/wiki/Tail_n_mail

Offres d'emplois autour de PostgreSQL en juillet

http://archives.postgresql.org/pgsql-jobs/2010-07/threads.php

PostgreSQL Local

Reuven Lerner donnera un cours de 5 jours sur PostgreSQL du 1er au 5 août au "Hi-Tech College" de Herzliya (Israël) : http://www.hi-tech.co.il/college/default.asp?PageID=12&CourseNum=4288
La FrOSCon 2010 aura lieu à St. Augustin (Allemagne) les 21 & 22 août 2010. Le PUG allemand a obtenu sa propre salle de dev. et est à la recherche de conférenciers. Plus de détails : http://andreas.scherbaum.la/blog/archives/711-FrOSCon-2010-PostgreSQL-devroom-Call-for-papers.html
L'appel à conférenciers pour la "West" est lancé jusqu'au 5 septembre 2010. Détails sur : http://www.postgresqlconference.org/

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.

(lien vers l'article original)

Revues

KaiGai Kohei reviewed Robert Haas's patch to add get_whatever_oid functionality.

Correctifs appliqués

Peter Eisentraut a commité :

In pgsql/src/interfaces/libpq/fe-connect.c, portability fixes for Solaris for requirepeer feature patch per report from Dave Page
Add more checks against altering typed tables. 1. Prohibit altering column type. 2. Prohibit changing inheritance. 3. Move checks from Exec to Prep phases in ALTER TABLE code. Backpatched to 9.0
In pgsql/doc/src/sgml/config.sgml, remove tab from SGML file
In pgsql/doc/src/sgml/datatype.sgml, tidy up boolean data type page. Thom Brown.
In pgsql/doc/src/sgml/datatype.sgml, fix typo.
In pgsql/doc/src/sgml/xfunc.sgml, add INSERT statement to example so that it can be reproduced from John Gage

Robert Haas a commité :

Change the default value of standard_conforming_strings to on. This change should be publicized to driver maintainers at once and release-noted as an incompatibility with previous releases.
Add restart_after_crash GUC. Normally, we automatically restart after a backend crash, but in some cases when PostgreSQL is invoked by clusterware it may be desirable to suppress this behavior, so we provide an option which does this. Since no existing GUC group quite fits, create a new group called "error handling options" for this and the previously undocumented GUC exit_on_error, which is now documented. Review by Fujii Masao.
Make hstore regression tests independent of standard_conforming_strings. Per buildfarm.
Make ECPG regression tests independent of standard_conforming_strings. Per buildfarm, again.
Add \conninfo command to psql, to show current connection info. David Christensen. Reviewed by Steve Singer. Some further changes by me.
In pgsql/src/bin/psql/command.c, have \conninfo mention the port even for local sockets. Per discussion with David Christensen, there can be multiple instances of PG accessible via local sockets, and you need the port to see which one you're actually connected to. David's original patch worked this way, but I inadvertently ripped it out during commit.
Centralize DML permissions-checking logic. Remove bespoke code in DoCopy and RI_Initial_Check, which now instead fabricate call ExecCheckRTPerms with a manufactured RangeTblEntry. This is intended to make it feasible for an enhanced security provider to actually make use of ExecutorCheckPerms_hook, but also has the advantage that RI_Initial_Check can allow use of the fast-path when column-level but not table-level permissions are present. KaiGai Kohei. Reviewed (in an earlier version) by Stephen Frost, and by me. Some further changes to the comments by me.
Add options to force quoting of all identifiers. I've added a quote_all_identifiers GUC which affects the behavior of the backend, and a --quote-all-identifiers argument to pg_dump and pg_dumpall which sets the GUC and also affects the quoting done internally by those applications. Design by Tom Lane; review by Alex Hunsaker; in response to bug #5488 filed by Hartmut Goebel.
In pgsql/src/bin/pg_dump/pg_dumpall.c, fix bogus server version in pg_dumpall --quote-all-identifiers.
In pgsql/src/backend/replication/walsender.c, add missing function prototype. Fujii Masao.
In pgsql/src/backend/access/transam/xact.c, avoid deep recursion when assigning XIDs to multiple levels of subxacts. Backpatch to 8.0. Andres Freund, with cleanup and adjustment for older branches by me.
In pgsql/src/bin/psql/command.c, have psql avoid describing local sockets as host names. We now use the phrase 'via local socket in' rather than 'on host' in both \c and \conninfo output, when applicable. Fujii Masao, with some kibitzing by me.
CREATE TABLE IF NOT EXISTS. Reviewed by Bernd Helmle.

Bruce Momjian a commité :

Properly replay CREATE TABLESPACE during crash recovery by deleting directory/symlink before creation. Report from Tom Lane. Backpatch to 9.0.
Prevent pg_upgrade from migrating databases that use reg* data types where the oid is not preserved by pg_upgrade (everything but pg_type). Update documentation. Per bug report from depstein@alliedtesting.com.
In contrib/pg_upgrade, adjust check_for_isn_and_int8_passing_mismatch() so it is called for all migrations. Backpatch to 9.0.
In pgsql/doc/src/sgml/ref/create_table.sgml, remove tabs from sgml file.

Magnus Hagander a commité :

Backpatch reservation of shared memory region during backend startup on Windows, so that memory allocated by starting third party DLLs doesn't end up conflicting. The same functionality has been in 8.3 and 8.4 for almost a year, and seems to have solved some of the more common shared memory errors on Windows.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

KaiGai Kohei sent in another revision of the patch to rework DML permisssion checks.
ITAGAKI Takahiro sent in another revision of the patch to implement more of SQL/MED.
Pavel Stehule sent in two more revisions of the patch to implement to_string() and to_array().
Etienne Dube sent in a patch to fix a "could not attach to shared memory" issue on Windows in the 8.2 branch.
ITAGAKI Takahiro and Pavel Stehule traded revisions of the string functions patch.
Marc Cousin sent in a patch to correct a cursor declaration in the "migrating from Oracle" section of the PL/pgsql docs.
Daniele Varrazzo sent in a patch to make more links from the libpq docs. This came from actual usage in psycopg.
Satoshi Nagayasu sent in another revision of the patch to redo the ECPG docs.
Alexander Korotkov sent in two more revisions of the patch to make levenshtein functions multibyte-aware.
Leonardo Francalanci sent in another revision of the patch to improve the CLUSTER implentation.
Pavel Stehule sent in two more revisions of the patch to enhance \ef and add \sf (show function) in psql.
Fujii Masao sent in another revision of the patch to do synchronous replication.
Teodor Sigaev sent in another flock of patches implementing K-Nearest-Neighbor for GiST indexes.
Alex Hunsaker sent in two more revisions of the patch to add functional depency inference to GROUP BY.
Kevin Grittner sent in another revision of the patch to make a more correct implementation of hypotenuse.
Joseph Adams sent in a patch to implement the JSON data type.
Mike Fowler sent in another revision of the patch to add XMLEXISTS to the grammar.
Joseph Adams sent in a patch to add a utf8_to_unicode() function, similar to the corresponding unicode_to_utf8() function. Among other things, this smooths the way for the upcoming JSON data type.

Nouvelles hebdomadaires de PostgreSQL - 18 juillet 2010

2010-07-21T21:14:17+00:00

PostgreSQL 9.0 beta 3 est disponible. Test ! [ndt: page Fr.] http://www.postgresql.org/developer/beta

L'appel à conférenciers pour la "West" est lancé jusqu'au 5 septembre 2010. Détails sur : http://www.postgresqlconference.org/

La première réunion du PUG de San Diego se fera au Cymer Inc. le 29 juillet 2010 : http://www.meetup.com/SD-PUG/calendar/14105562/

Les nouveautés des produits dérivés

psycopg2 2.2.2, un connecteur Python pour PostgreSQL : http://initd.org/psycopg/

Offres d'emplois autour de PostgreSQL en juillet

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

PostgreSQL Local

L'OSCON aura lieu à Portland (Oregon) du 19 au 23 juillet 2010 : http://www.oscon.com/oscon2010
Reuven Lerner donnera un cours de 5 jours sur PostgreSQL du 1er au 5 août au "Hi-Tech College" de Herzliya (Israël) : http://www.hi-tech.co.il/college/default.asp?PageID=12&CourseNum=4288
La FrOSCon 2010 aura lieu à St. Augustin (Allemagne) les 21 & 22 août 2010. Le PUG allemand a obtenu sa propre salle de dev. et est à la recherche de conférenciers. Plus de détails : http://andreas.scherbaum.la/blog/archives/711-FrOSCon-2010-PostgreSQL-devroom-Call-for-papers.html

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 et Devrim Gunduz. Traduction par l'équipe PostgreSQLFr sous licence CC BY-NC-SA.

(lien vers l'article original)

Revues

KaiGai Kohei reviewed Robert Haas's patch to add get_whatever_oid functionality.

Correctifs appliqués

Bruce Momjian a commité :

Bump minor library version numbers, for 9.1 release.
In pgsql/src/tools/RELEASE_CHANGES, document bump of minor library version numbers.
In pgsql/doc/src/sgml/release-9.0.sgml, spellcheck 9.0 release notes.
In pgsql/doc/src/sgml/release-9.0.sgml, 9.0 release note improvements Erik Rijkers
In pgsql/doc/src/sgml/release-9.0.sgml, restore pl/pgsql default install release note item.
In pg_upgrade, prevent psql AUTOCOMMIT=off by not loading .psqlrc.
In pgsql/src/tools/fsync/test_fsync.c, print each test_fsync description while test is running, rather than at the end.
In pgsql/contrib/pg_upgrade/exec.c, in pg_upgrade, report /bin directory checks independent of /data checks.
In pgsql/contrib/pg_upgrade/option.c, remove incorrect email address for pg_upgrade bug reports.
In pgsql/contrib/pg_upgrade/server.c, on Win32, pg_upgrade cannot sent any server log output to the log file because of file access limitations on that platform.
Backpatch pg_upgrade fixes to 9.0: 1. In pg_upgrade, prevent psql AUTOCOMMIT=off by not loading .psqlrc. 2. In pg_upgrade, report /bin directory checks independent of /data checks. 3. Remove incorrect email address for pg_upgrade bug reports. 4. On Win32, pg_upgrade cannot sent any server log output to the log file because of file access limitations on that platform.
In pgsql/src/backend/commands/tablespace.c, simplify missing tablespace replay error hint message, but only in HEAD so we don't need to re-translate for 9.0.
In pgsql/src/interfaces/libpq/fe-connect.c, add SO_PEERCRED check in new unix domain socket permission checking code.

Tom Lane a commité :

Make NestLoop plan nodes pass outer-relation variables into their inner relation using the general PARAM_EXEC executor parameter mechanism, rather than the ad-hoc kluge of passing the outer tuple down through ExecReScan. The previous method was hard to understand and could never be extended to handle parameters coming from multiple join levels. This patch doesn't change the set of possible plans nor have any significant performance effect, but it's necessary infrastructure for future generalization of the concept of an inner indexscan plan. ExecReScan's second parameter is now unused, so it's removed.
Teach EXPLAIN to print PARAM_EXEC Params as the referenced expressions, rather than just $N. This brings the display of nestloop-inner-indexscan plans back to where it's been, and incidentally improves the display of SubPlan parameters as well. In passing, simplify the EXPLAIN code by having it deal primarily in the PlanState tree rather than separately searching Plan and PlanState trees. This is noticeably cleaner for subplans, and about a wash elsewhere. One small difference from previous behavior is that EXPLAIN will no longer qualify local variable references in inner-indexscan plan nodes, since it no longer sees such nodes as possibly referencing multiple tables. Vars referenced through PARAM_EXEC Params are still forcibly qualified, though, so I don't think the display is any more confusing than before. Adjust a couple of examples in the documentation to match this behavior.
Allow full SSL certificate verification (wherein libpq checks its host name parameter against server cert's CN field) to succeed in the case where both host and hostaddr are specified. As with the existing precedents for Kerberos, GSSAPI, SSPI, it is the calling application's responsibility that host and hostaddr match up --- we just use the host name as given. Per bug #5559 from Christopher Head. In passing, make the error handling and messages for the no-host-name-given failure more consistent among these four cases, and correct a lie in the documentation: we don't attempt to reverse-lookup host from hostaddr if host is missing. Back-patch to 8.4 where SSL cert verification was introduced.
In pgsql/src/bin/pg_dump/pg_dump.c, fix several problems in pg_dump's handling of SQL/MED objects, notably failure to dump a PUBLIC user mapping correctly, as per bug #5560 from Shigeru Hanada. Use the pg_user_mappings view rather than trying to access pg_user_mapping directly, so that the code doesn't fail when run by a non-superuser. And clean up some minor carelessness such as unsafe usage of fmtId(). Back-patch to 8.4 where this code was added.
In pgsql/doc/src/sgml/high-availability.sgml, use an <xref> for restore_command reference. Marko Tiikkaja.
In pgsql/src/backend/commands/opclasscmds.c, remove duplicate code in DefineOpFamily(). The code was probably meant to be this way all along, since the subroutine CreateOpFamily previously had only one caller. But it wasn't. KaiGai Kohei.
In pgsql/src/backend/executor/execUtils.c, remove a sanity check in the exclusion-constraint code that prevented users from defining non-self-conflicting constraints. Jeff Davis. Note: I (tgl) objected to removing this check in 9.0 on the grounds that it was an important sanity check in new, poorly tested code. However, it should be all right to remove it for 9.1, since we'll get field testing from the 9.0 branch.
Add support for dividing money by money (yielding a float8 result) and for casting between money and numeric. Andy Balholm, reviewed by Kevin Grittner
Add a log_file_mode GUC that allows control of the file permissions set on log files created by the syslogger process. In passing, make unix_file_permissions display its value in octal, same as log_file_mode now does. Martin Pihlak
In pgsql/src/interfaces/libpq/fe-connect.c, fix thinko in recent patch: 'sock' should be 'conn->sock'.
In pgsql/src/interfaces/libpq/fe-connect.c, fix up poor handling of unsupported-platform case in requirepeer patch.
Allow ORDER BY/GROUP BY/etc items to match targetlist items regardless of any implicit casting previously applied to the targetlist item. This is reasonable because the implicit cast, by definition, wasn't written by the user; so we are preserving the expected behavior that ORDER BY items match textually equivalent tlist items. The case never arose before because there couldn't be any implicit casting of a top-level SELECT item before we process ORDER BY etc. But now it can arise in the context of aggregates containing ORDER BY clauses, since the "targetlist" is the already-casted list of arguments for the aggregate. The net effect is that the datatype used for ORDER BY/DISTINCT purposes is the aggregate's declared input type, not that of the original input column; which is a bit debatable but not horrendous, and to do otherwise would require major rework that doesn't seem justified. Per bug #5564 from Daniel Grace. Back-patch to 9.0 where aggregate ORDER BY was implemented.
In pgsql/src/backend/utils/error/elog.c, remove unnecessary "Not safe to send CSV data" complaint from elog.c's fallback path when CSV logging is configured but not yet operational. It's sufficient to send the message to stderr, as we were already doing, and the "Not safe" gripe has already confused at least two core members ... Backpatch to 9.0, but not further --- doesn't seem appropriate to change this behavior in stable branches.

Heikki Linnakangas a commité :

In pgsql/src/backend/utils/mmgr/portalmem.c, oops, in the previous fix to prevent a cursor that's being used in a FOR loop from being dropped, I missed subtransaction cleanup. Pinned portals must be dropped at subtransaction cleanup just as they are at main transaction cleanup. Per bug #5556 by Robert Walker. Backpatch to 8.0, 7.4 didn't have subtransactions.
Add a paragraph explaining what restartpoints are. Mention that wal_keep_segments does not take effect during recovery. Fujii Masao
In pgsql/doc/src/sgml/wal.sgml, fix typo spotted by Thom Brown.

Peter Eisentraut a commité :

Add server authentication over Unix-domain sockets. This adds a libpq connection parameter requirepeer that specifies the user name that the server process is expected to run under. Reviewed by KaiGai Kohei.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

KaiGai Kohei sent in another revision of the patch reworking DML permissions.
Marko (johto) Tiikkaja sent in another WIP patch implementing writeable CTEs.
Greg Smith sent in another revision of the patch to make pgbench 64-bit clean.
Pavel Stehule sent in two more revisions of the patch to add left, right, reverse and concat functions to core, and printf and concat_ws functions to contrib.
Markus Wanner sent in a flock of patches to add a background worker infrastructure which could be used, for example, in doing parallel queries.
Alexander Korotkov sent in another revision of the patch to speed up levenshtein distance for multi-byte character sets.
Tom Lane sent in a patch to trace only PlanState trees in EXPLAIN. Currently, both PlanState and Plan get traced.
Peter Eisentraut sent in a proof-of-concept patch to implement per-column collation.
Mark Wong sent in another version of the patch to allow multiple -f's in the invocation of psql.
Pavel Stehule sent in another revision of the patch to preload text search dictionaries.
Robert Haas sent in another revision of the patch to suppress automatic recovery after a back-end crash, per review from Fujii Masao.
KaiGai Kohei sent in two separate patches to add security labels to database objects.
Fujii Masao sent in a patch intended to allow various levels of synchronous replication via a replication_mode parameter for recovery.conf in Hot Standby/Streaming Replication. It also provides some infrastructure for a quorum commit feature.
Yeb Havinga sent in another revision of the patch to allow for five-key syscaches, which is infrastructure for, among other things, K-Nearest-Neighbor GiST searches.
Robert Haas sent in a patch to make standard_conforming_strings on by default.
Simon Riggs sent in another revision of the patch to reduce the lock level required by ALTER TABLE, CREATE TRIGGER and CREATE RULE.
Boxuan Zhai sent in another revision of the patch to add MERGE.
Jeff Davis sent in another revision of the patch to add a "not equals" operator for contrib/btree_gist.
Brendan Jurd sent in another revision of the to_string(), to_array(), etc. patch.
Jan Urbanski sent in another revision of the patch to add functionality to \ef (edit function) and add \sf (show function) to psql.
Kevin Grittner sent in another revision of the patch to do true serializability.
David Christensen sent in another revision of the patch to add \conninfo to psql.
Bruce Momjian sent in three revisions of a patch intended to fix a breakage of CREATE TABLESPACE during crash recovery.

Hot Standby : un exemple concret

2010-07-19T07:21:00+00:00

Nous sommes actuellement en train de tester la version 9.0beta3 sur les serveurs de postgresql.fr

J'ai passé une partie de mon week-end à documenter la mise en place d'une réplication Hot Standby en Streaming entre les deux serveurs.

Avec le recul je me rend compte que cette doc peut être utile à d'autres donc j'ai pris le temps de la publier :

http://www.postgresql.fr/admin:installation_9.0

Il s'agit simplement d'un tutoriel très succinct qui montre pas à pas chaque étapes de l'installation. Je ne suis pas rentré dans les détails et c'est volontaire si vous chercher une doc plus complète, je vous conseille les articles de Guillaume parus dans Linux Mag l'année dernière :

J'espère que mon how-to prouve à quel point la réplication est devenue un jeu d'enfant avec PostgreSQL.

Bien sur on est encore en phase Beta, la version stable devrait arriver cet automne. D'ici là je vous encourage fortement à installer la version 9.0beta, à tester le Hot Standby par vous même et à remonter les éventuels bugs rencontrés

Nouvelles hebdomadaires de PostgreSQL - 11 juillet 2010

2010-07-18T00:18:19+00:00

PostgreSQL 9.0 beta 3 sera bientôt disponible [ndt: article dédié].Préparez-vous à tester ! http://www.postgresql.org/developer/beta

Rassemblement PostgreSQL/PostGIS le 14 juillet 2010 à 18h, à Zurich (Suisse) au bOm kultur café & bar à l'ETH [ndt: institut fédéral technologique] Zurich. Informations et inscriptions (informelles) : http://www.gis.hsr.ch/wiki/Agenda

Reuven Lerner donnera un cours de 5 jours sur PostgreSQL du 1er au 5 août au "Hi-Tech College" de Herzliya (Israël) : http://www.hi-tech.co.il/college/default.asp?PageID=12&CourseNum=4288

Les nouveautés des produits dérivés

Benetl 3.5, un ETL pour fichiers utilisant PostgreSQL : http://www.benetl.net
DataArchitect 4.2, un outil de dessin de diagramme relationnel et d'ingénierie inverse compatible PostgreSQL : http://www.thekompany.com/products/dataarchitect/
PostgreSQL Maestro 10.7, un outil d'administration graphique pour PostgreSQL : http://www.sqlmaestro.com/products/postgresql/maestro/
Muldis-D 0.130.0, une spécification pour un langage objet-relationnel prévu pour utiliser, entre autres systèmes, PostgreSQL : http://muldis.com/Muldis_D.html
RHQ 3.0.0, une application de gestion et de surveillance : http://rhq-project.org/

Offres d'emplois autour de PostgreSQL en juillet

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

PostgreSQL Local

Le PDXPUG Day est programmé pour le 18 juillet 2010 à "l'Oregon Convention Center" à Portland. D'avantage d'informations : http://wiki.postgresql.org/wiki/PDXPUGDay2010
L'OSCON aura lieu à Portland (Oregon) du 19 au 23 juillet 2010 : http://www.oscon.com/oscon2010
La FrOSCon 2010 aura lieu à St. Augustin, Allemagne les 21 & 22 août 2010. Le PUG allemand a obtenu sa propre salle de dev. et est à la recherche de conférenciers. Plus de détails : http://andreas.scherbaum.la/blog/archives/711-FrOSCon-2010-PostgreSQL-devroom-Call-for-papers.html

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.

(lien vers l'article original)

Revues

KaiGai Kohei reviewed Robert Haas's patch to add get_whatever_oid functionality.

Correctifs appliqués

Tom Lane a commité :

Improve pg_dump's checkSeek() function to verify the functioning of ftello as well as fseeko, and to not assume that fseeko(fp, 0, SEEK_CUR) proves anything. Also improve some related comments. Per my observation that the SEEK_CUR test didn't actually work on some platforms, and subsequent discussion with Robert Haas. Back-patch to 8.4. In earlier releases it's not that important whether we get the hasSeek test right, but with parallel restore it matters.
In pgsql/doc/src/sgml/release-9.0.sgml, add compatibility note warning that plpgsql is now stricter about the column datatypes of composite results, per gripe from Marcel Asio. Some desultory copy-editing of plpgsql-related sections of the release notes.
Get rid of some more stuff in pg_upgrade that duplicates c.h or port.h.
In pgsql/doc/src/sgml/datatype.sgml, fix assorted misstatements and poor wording in the descriptions of the I/O formats for geometric types. Per bug #5536 from Jon Strait, and my own testing. Back-patch to all supported branches, since this doco has been wrong right along -- we certainly haven't changed the I/O behavior of these types in many years.
Replace max_standby_delay with two parameters, max_standby_archive_delay and max_standby_streaming_delay, and revise the implementation to avoid assuming that timestamps found in WAL records can meaningfully be compared to clock time on the standby server. Instead, the delay limits are compared to the elapsed time since we last obtained a new WAL segment from archive or since we were last "caught up" to WAL data arriving via streaming replication. This avoids problems with clock skew between primary and standby, as well as other corner cases that the original coding would misbehave in, such as the primary server having significant idle time between transactions. Per my complaint some time ago and considerable ensuing discussion. Do some desultory editing on the hot standby documentation, too.
Make vacuum_defer_cleanup_age be PGC_SIGHUP level, since it's not sensible to have different values in different processes of the primary server. Also put it into the "Streaming Replication" GUC category; it doesn't belong in "Standby Servers" because you use it on the master not the standby. In passing also correct guc.c's idea of wal_keep_segments' category.
In pgsql/src/backend/access/transam/xlog.c, don't set recoveryLastXTime when replaying a checkpoint --- that was a bogus idea from the start since the variable is only meant to track commit/abort events. This patch reverts the logic around the variable to what it was in 8.4, except that the value is now kept in shared memory rather than a static variable, so that it can be reported correctly by CreateRestartPoint (which is executed in the bgwriter).
Split the LDFLAGS make variable into two parts: LDFLAGS is now used for linking both executables and shared libraries, and we add on LDFLAGS_EX when linking executables or LDFLAGS_SL when linking shared libraries. This provides a significantly cleaner way of dealing with link-time switches than the former behavior. Also, make sure that the various platform-specific %.so: %.o rules incorporate LDFLAGS and LDFLAGS_SL; most of them missed that before. (I did not add these variables for the platforms that invoke $(LD) directly, however. It's not clear if we can do that safely, since for the most part we assume these variables use CC command-line syntax.) Per gripe from Aaron Swenson and subsequent investigation.
Fix a few single-file (MODULES, not MODULE_big) contrib makefiles that were supposing that they should set SHLIB_LINK rather than LDFLAGS_SL. Since these don't go through Makefile.shlib that was a no-op on most platforms. Also regularize the few platform-specific Makefiles that did pay attention to SHLIB_LINK: it seems that the real value of that is to pull in BE_DLLLIBS, so do that instead. Per buildfarm failures on cygwin.
In pgsql/src/makefiles/pgxs.mk, make sure LDFLAGS come before LIBS when linking contrib programs. Solaris, at least, seems to be sensitive to the relative order of -L and -l switches, so this is needed. Per buildfarm results.
In pgsql/src/makefiles/pgxs.mk, dept. of third thoughts: PG_LIBS may contain a -L switch, so it had better stay in front of LDFLAGS.
In pgsql/src/makefiles/Makefile.aix, allow for LDFLAGS_SL already having a value in Makefile.aix. Per buildfarm results.
In pgsql/src/Makefile.shlib, still more third thoughts: when linking shared libraries, LDFLAGS probably needs to appear before anything placed in SHLIB_LINK. This is because SHLIB_LINK is typically a subset of LIBS, and LIBS has to appear after LDFLAGS on platforms that are sensitive to the relative order of -L and -l switches.
In pgsql/src/backend/utils/mb/mbutils.c, undo pgindent breakage (again). Per buildfarm.
In pgsql/src/Makefile.global.in, accept slightly grotty coding in Makefile.global in order to keep the -L flag for src/port/ in front of any -L flags placed in LDFLAGS by configure. This undoes an L-flag-ordering change that I had thought would be safe, but seems to be making at least one buildfarm member fail --- the only theory for orca's failure that I can think of is that it's got an old copy of libpgport.a in /usr/lib. Also allow for LDFLAGS_SL to be set by contrib makefiles before they invoke Makefile.global.
In pgsql/src/backend/utils/mb/mbutils.c, adjust mbutils.c so it won't get broken by future pgindent runs. To do that, replace L'\0' by (WCHAR) 0. Perhaps someday we should teach pgindent about wide-character literals, but so long as this is the only use-case in the entire Postgres sources, a workaround seems easier.
Fix "cannot handle unplanned sub-select" error that can occur when a sub-select contains a join alias reference that expands into an expression containing another sub-select. Per yesterday's report from Merlin Moncure and subsequent off-list investigation. Back-patch to 7.4. Older versions didn't attempt to flatten sub-selects in ways that would trigger this problem.
Fix variant float8 expected files to have exactly the expected spacing. This wasn't important when we used diff's -w (--ignore-all-space) option to compare regression result files, but it is now. Per buildfarm member canary, which evidently has been offline since we did that in November, but came to life again today.
In pgsql/src/backend/access/transam/xlogutils.c, update obsolete comment. Noted by Josh Tolley.
In pgsql/doc/src/sgml/ref/create_operator.sgml, add a cross-reference to precedence information to CREATE OPERATOR's documentation. Per suggestion from Marc Cousin.
In pgsql/src/pl/plpython/plpython.c, minor kibitzing on previous patch from Peter Eisentraut which guards against using PL/PythonU2 and PL/PythonU3 in the same session: no need to run check more than once. (_PG_init should be called only once anyway, but as long as it's got an internal guard against repeat calls, that should be in front of the version check.)
Stamp HEAD as 9.1devel. (And there was much rejoicing.)
In pgsql/src/backend/utils/adt/ruleutils.c, fix ruleutils' get_variable() to print something useful for Vars referencing resjunk outputs of subquery tlists, instead of throwing an error. Per bug #5548 from Daniel Grace. We might at some point find we ought to back-patch this further than 9.0, but I think that such Vars can only occur as resjunk members of upper-level tlists, in which case the problem can't arise because prior versions didn't print resjunk tlist items in EXPLAIN VERBOSE.
In pgsql/src/backend/utils/cache/lsyscache.c, avoid an Assert failure in deconstruct_array() by making get_attstatsslot() use the actual element type of the array it's disassembling, rather than trusting the type OID passed in by its caller. This is needed because sometimes the planner passes in a type OID that's only binary-compatible with the target column's type, rather than being an exact match. Per an example from Bernd Helmle. Possibly we should refactor get_attstatsslot/free_attstatsslot to not expect the caller to supply type ID data at all, but for now I'll just do the minimum-change fix. Back-patch to 7.4. Bernd's test case only crashes back to 8.0, but since these subroutines are the same in 7.4, I suspect there may be variant cases that would crash 7.4 as well.
In pgsql/doc/src/sgml/sources.sgml, add a note about preferred window width to the section about code formatting conventions.

Bruce Momjian a commité :

In pgsql/doc/src/sgml/high-availability.sgml, remove tab from SGML.
Add new Non-Durable Settings documentation section. Document that synchronous_commit can lose transactions in a db crash, not just a OS crash.
Fix doc double-wording in non-durable patch. Report from Thom Brown.
In pgsql/src/backend/access/transam/xact.c, add C comment about why synchronous_commit=off behavior can lose committed transactions in a postmaster crash.
In pgsql/doc/src/sgml/config.sgml, document that shared_preload_libraries and local_preload_libraries lowercase the library names, unless double-quoted.
In documentation, use "lower case"/"upper case" consistently (use space between words).
In pgsql/doc/src/sgml/config.sgml, document that /bin/true on Windows is implemented by 'REM'.
In pgsql/doc/src/sgml/release-9.0.sgml, update 9.0 release notes so streaming replication and hot standby is not assumed to require continuous archiving. Per report from Fujii Masao.
In pgsql/contrib/pg_upgrade/pg_upgrade.h, remove port.h prototypes from pg_upgrade.h, per report from Robert Haas.
In pgsql/src/backend/commands/tablespace.c, issue 'mkdir' hint when replying CREATE TABLESPACE in recovery mode. Per idea from Fujii Masao.
Add CVS tags to pg_upgrade and pg_upgrade_support files, per request from Tom Lane.
Add copyrights to pg_upgrade and pg_upgrade_tools files, per Tom Lane.
Make pg_upgrade copyrights just 2010, not 2010-2010.
In pgsql/doc/src/sgml/func.sgml, document more clearly on XML namespaces inside xpath function. Nikolay Samokhvalov.
In pgsql/doc/src/sgml/config.sgml, remove SGML tab.
In pgsql/src/tools/fsync/test_fsync.c, report test_fynsc times in tests per second, instead of total seconds.
In pgsql/src/tools/fsync/test_fsync.c, simplify test_fsync duration computation.
Update pgindent testing instructions.
pgindent run for 9.0, second run.
In pgsql/src/tools/pgindent/README, mention why one C file fails pgindent.
In pgsql/doc/src/sgml/wal.sgml, document the interaction of write-barrier-enabled file systems, and BBU caches, per June email thread.
In pgsql/doc/src/sgml/wal.sgml, doc change: effected -> affected, per correction from Matthew Wakeling.
In pgsql/doc/src/sgml/release-9.0.sgml, update release notes for 9.0 beta 3.
Properly report errno/out-of-disk-space error from pg_upgrade when in copy mode, per report from depstein@alliedtesting.com. Patch suggestion from Magnus. Backpatch to 9.0.X.

Peter Eisentraut a commité :

In pgsql/doc/src/sgml/sources.sgml, add guidelines for formatting errcontext strings
In pgsql/doc/src/sgml/datatype.sgml, add note clarifying that XML fragments don't accept DTDs, per complaint from Craig Ringer.
Use different function names for plpython3 handlers, to avoid clashes in pg_pltemplate. This should have a catversion bump, but it's still being debated whether it's worth it during beta.
Message tuning.
In pgsql/doc/src/sgml/plpython.sgml, add note that using PL/Python 2 and 3 in the same session will probably crash.
Install safeguard against running PL/Python 2 and 3 in the same session.
Translation updates for 9.0beta3.
In pgsql/doc/src/sgml/plperl.sgml, some small changes: wrapped long code-lines for pdf, fix typo. Erik Rijkers

Robert Haas a commité :

In pgsql/src/backend/access/transam/xlog.c, emode_for_corrupt_record shouldn't reduce LOG messages to WARNING. In non-interactive sessions, WARNING sorts below LOG.
In pgsql/src/backend/commands/tablecmds.c, allow ALTER TABLE .. SET TABLESPACE to be interrupted. Backpatch to 8.0, where tablespaces were introduced. Guillaume Lelarge
In pgsql/src/port/copydir.c, allow copydir() to be interrupted. This makes ALTER DATABASE .. SET TABLESPACE and CREATE DATABASE more sensitive to interrupts. Backpatch to 8.4, where ALTER DATABASE .. SET TABLESPACE was introduced. We could go back further, but in the absence of complaints about the CREATE DATABASE case it doesn't seem worth it. Guillaume Lelarge, with a small correction by me.
Move copydir.c from src/port to src/backend/storage/file. The previous commit to make copydir() interruptible prevented postgres.exe from linking on MinGW and Cygwin, because on those platforms libpgport_srv.a can't freely reference symbols defined by the backend. Since that code is already backend-specific anyway, just move the whole file into the backend rather than adding further kludges to deal with the symbols needed by CHECK_FOR_INTERRUPTS(). This probably needs some further cleanup, but this commit just moves the file as-is, which should hopefully be enough to turn the buildfarm green again.
Remove hstore % text[] operator; use slice() function instead. David Wheeler, with one small correction by me.
Additional cross-references to window functions documentation. Erik Rijkers.
Allow REASSIGNED OWNED to handle opclasses and opfamilies. Backpatch to 8.3, which is as far back as we have opfamilies. The opclass portion could probably be backpatched to 8.2, when REASSIGN OWNED was added, but for now I have not done that. Asko Tiidumaa, with minor adjustments by me.
Support setting the keepalive idle time on MacOS X. MacOS X uses TCP_KEEPALIVE rather than TCP_KEEPIDLE for this purpose. Thanks to Fujii Masao for the review.
Make log_temp_files based on kB, and revert docs & comments to match. Per extensive discussion on pgsql-hackers. We are deliberately not back-patching this even though the behavior of 8.3 and 8.4 is unquestionably broken, for fear of breaking existing users of this parameter. This incompatibility should be release-noted.
Add a hook in ExecCheckRTPerms(). This hook allows a loadable module to gain control when table permissions are checked. It is expected to be used by an eventual SE-PostgreSQL implementation, but there are other possible applications as well. A sample contrib module can be found in the archives at: http://archives.postgresql.org/pgsql-hackers/2010-05/msg01095.php Robert Haas and Stephen Frost.
In pgsql/doc/src/sgml/ref/psql-ref.sgml, clarify that "psql -c" ignores psqlrc files. Tim Landscheidt

Andrew Dunstan a commité :

In pgsql/doc/src/sgml/release-9.0.sgml, correct missing/misspelled surname.
In pgsql/src/tools/msvc/Mkvcbuild.pm, unbreak MSVC builds by removing copydir.c from list of libpgport files

Heikki Linnakangas a commité :

stringToNode() and deparse_expression_pretty() crash on invalid input, but we have nevertheless exposed them to users via pg_get_expr(). It would be too much maintenance effort to rigorously check the input, so put a hack in place instead to restrict pg_get_expr() so that the argument must come from one of the system catalog columns known to contain valid expressions. Per report from Rushabh Lathia. Backpatch to 7.4 which is the oldest supported version at the moment.
The previous fix in CVS HEAD and 8.4 for handling the case where a cursor being used in a PL/pgSQL FOR loop is closed was inadequate, as Tom Lane pointed out. The bug affects FOR statement variants too, because you can close an implicitly created cursor too by guessing the "<unnamed portal X>" name created for it. To fix that, "pin" the portal to prevent it from being dropped while it's being used in a PL/pgSQL FOR loop. Backpatch all the way to 7.4 which is the oldest supported version.

Magnus Hagander a commité :

Add support for TCP keepalives on Windows, both for backend and the new libpq support.
Make the Windows tcp keepalive support depend on the existance of the SIO_KEEPALIVE_VALS define instead of just WIN32, since MingW doesn't support this API (yet?).

Marc Fournier a commité :

tag beta3

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

Robert Haas sent in another revision of the patch to suppress automatic recovery after backend crash. This is for a volatile caching version of PostgreSQL.
Robert Haas sent in another revision of the patch to add get_whatever_oid functionality.
Magnus Hagander sent in two revisions of a patch to fix keepalives on Win32.
Robert Haas sent in a patch to implmenet a warning message in pg_standby.
Mike Fowler sent in another revision of the xpath_exists patch.
Peter Eisentraut sent in another revision of the patch to allow server authentication over Unix-domain sockets.
Mike Fowler sent in another revision of patch to add XMLEXISTS to the grammar.
Robert Haas sent in two revisions of a patch to fix keepalives on OSX.
Bruce Momjian sent in a patch to show a hint only in recovery after a crash of Hot Standby/Streaming Replication.
Fujii Masao sent in an updated patch to fix the docs re: checkpoint_segments and keep_wal_segments for Hot Standby/Streaming Replication.
Martin Pihlak sent in two revisions of a patch to add a GUC log_file_mode which allows specifying the creation mode for log files. This would enable, for example, permitting readers other than the system PostgreSQL user to read the log files PostgreSQL generates.
Teodor Sigaev sent in a patch to implement more accurate cost estimation function for GIN index scans.
Markus Shiltknecht sent in a patch to add a lock-based dynamic shared memory allocator, which lets components delay memory allocation rather than allocate all needed memory in advance.
Pavel Stehule sent in a patch to add parameters to DO statements.
Robert Haas sent in three more revisions of a patch to implement get_whatever_oid, a refactoring which to a large extent centralizes get_*_oid logic.
Robert Haas sent in a patch to fix log_temp_files docs and comments to say kilobytes rather than bytes.
Greg Smith sent in another revision of the patch to make pgbench more 64-bit-clean.
ITAGAKI Takahiro sent in another revision of the patch to help make CLUSTER behave better.
Mike Fowler sent in two more revisions of a patch to add an xml_is_well_formed function.
Rajanikant Chirmade sent in a patch to make downcase_truncate_identifier() multibyte-character-aware.
Pavel Stehule sent in two more revisions of the string functions for 9.1.
Robert Haas sent in another revision of the patch to include the backend ID in relpath of temp rels.
Pavel Baros sent in another revision of the patch to add materialized views.
Kevin Grittner sent in another revision of the patch to implement predicate locking, in part a prerequisite for better serialization.
Robert Haas sent in a patch to slim down the representation of numerics by about two bytes.
Zhai Boxuan sent in a patch to implement a MERGE command.
Erik Rijkers sent in a patch to fix the contrib makefile to include the stringfunc patch.

GIT, cette nouvelle mode

2010-07-15T21:09:00+00:00

Donc PostgreSQL passe à git mi-août. Du coup, un peu tout le monde y passe. pgAdmin commence son passage ce soir (avec le dépôt pgagent par exemple). Slony se pose officiellement la question. Quant aux dépôts de PostgreSQLfr, ils y sont passés depuis un mois en gros.

Je trouve ça plutôt bien. Ça uniformise les dépôts sur un système véritablement excellent. Pour une fois qu'on uniformise vers le haut, on ne va pas se plaindre

Manuel 9.0 beta 3 disponible

2010-07-15T11:27:00+00:00

Et non, pas de vacances pour moi pour l'instant. Les deux semaines d'inactivité sur ce blog ont une raison : la mise à jour de la traduction du manuel en beta3, mais aussi et surtout du travail sur pgAdmin (dont je parlerais plus tard, certainement en fin de semaine).

Bref. Tout ça pour dire que la traduction française du manuel de PostgreSQL 9.0 beta 3 est disponible. Normalement, tout est traduit. Peut-être mal, il va falloir que je fasse une passe importante de relecture. En attendant, un lien pour consulter la doc en ligne et un lien pour récupérer le PDF.

Merci de me rapporter tout soucis constaté dans la traduction.

Update: correction du lien vers le PDF. Merci à "Fly".

Sortie de la verion beta 3 de PostgreSQL 9.0

2010-07-13T07:18:34+00:00

La 3ème version beta de PostgreSQL 9.0 est désormais disponible. Cette version contient de nombreuses corrections et plusieurs changements par rapport à la Beta 2, notamment un dépoussiérage final de la Streaming Replication et du Hot Standby. N'hésitez pas à télécharger, installer et tester cette version pour aider les développeurs à avancer vers la version finale. Plusieurs changement significatifs ont été introduit dans la Beta3, ce qui implique que certaines fonctionnalités doivent être re-testées, notamment :

   *  Corrections du hot standby
   *  Correction de la gestion des tableaux en plpython
   *  Plusieurs corrections pour dblink
   *  Support du TCP keepalive dans libpq
   *  Correction du comportement de checkSeek() sur les platformes anciennes

Notez que suite à un changement du catalogue système, un initdb et un reload sont nécessaires pour mettre à jour depuis la version 9.0Beta1. C'est une belle opportunité pour tester pg_upgrade à partir de la version Beta2 ou antérieure.

Si vous avez la possibilité de réaliser des tests, rendez-vous sur la page dédiée aux tests de la version beta

Nous rappelons que les versions beta ne sont pas stables et qu'elles ne doivent pas être utilisées en production. Elles sont uniquement destinées aux tests. D'autres versions beta et des versions candidates seront produites dans les semaines à venir…

L'annonce officielle : http://www.postgresql.org/about/news.1220
Lien de téléchargement : http://www.postgresql.org/ftp/source/v9.0beta3/

Comment un problème constaté chez un client peut se transformer en un nouveau patch pour PostgreSQL

2010-07-03T09:45:00+00:00

Mardi dernier, un client en support nous appelle à cause d'un problème d'espace disque. Il est en version 8.2. Il dispose de place libre sur d'autres partitions. Rien de plus simple. Il suffit de créer un tablespace sur une des partitions où il reste suffisamment d'espace et d'y déplacer quelques objets pour faire de la place sur le répertoire principal des données. Tout se passe bien : création du répertoire, ajout du tablespace (avec CREATE TABLESPACE), choix de la table à déplacer, et déplacement de la table (avec un ALTER TABLE). Malheureusement, l'opération prends du temps, beaucoup de temps. Et les performances du serveur ont commencé à en pâtir. Le client a voulu interrompre l'opération, quitte à la reprendre plus tard. Pas de soucis, un simple Ctrl-C doit suffire. Et bien non, Ctrl-C et pg_cancel_backend() nous indiquaient bien que la demande d'annulation avait été envoyée mais les opérations sur le disque continuaient et psql ne nous rendait pas la main. Nous avons donc été forcés d'attendre la fin de l'opération.

Pendant ce temps, j'ai commencé à tester sur mon portable et a fouillé dans le code. Et j'ai fini par me rendre compte que rien ne permettait une prise en compte du signal pendant la copie. Autrement dit, vous lancez un changement de tablespace pour la table X de 50 Go, vous essayez de l'annuler au tout début, il vous faudra quand même attendre la fin de la copie des 50 Go pour que votre demande d'annulation soit prise en compte. Très dommageable. Il faut corriger ça. Tout le code se trouve dans la fonction copy_relation_data du fichier src/backend/commands/tablecmds.c. Une boucle s'occupe de la copie :

 for (blkno = 0; blkno < nblocks; blkno++)
 {    
     smgrread(src, forkNum, blkno, buf);
 
     /* XLOG stuff */
     if (use_wal)
         log_newpage(&dst->smgr_rnode, forkNum, blkno, page);
 
     /*   
      * Now write the page.  We say isTemp = true even if it's not a temp
      * rel, because there's no need for smgr to schedule an fsync for this
      * write; we'll do it ourselves below.
      */
     smgrextend(dst, forkNum, blkno, buf, true);
 }

Autrement dit, on lit chaque bloc du fichier source, que l'on copie dans le fichier destination. Une bête copie bloc par bloc, avec aucun moyen de l'interrompre.

De mes lectures dans pgsql-hackers, je me rappelais qu'il existe une fonction appelée CHECK_FOR_INTERRUPTS faisant exactement le travail dont j'avais besoin. J'ai donc uniquement ajouté un appel à cette fonction au début de la boucle, ce qui donne au final :

 for (blkno = 0; blkno < nblocks; blkno++)
 {    
     /* If we got a cancel signal during the copy of the data, quit */
     CHECK_FOR_INTERRUPTS();
    
     smgrread(src, forkNum, blkno, buf);
     
     /* XLOG stuff */
     if (use_wal)
         log_newpage(&dst->smgr_rnode, forkNum, blkno, page);
   
     /*   
      * Now write the page.  We say isTemp = true even if it's not a temp
      * rel, because there's no need for smgr to schedule an fsync for this
      * write; we'll do it ourselves below.
      */
     smgrextend(dst, forkNum, blkno, buf, true);
 }

Une compilation et quelques tests après, je me suis aperçu que tout fonctionnait comme je le souhaitais. L'annulation se fait exactement au moment où je la demande.

J'ai corrigé aussi le déplacement d'une base de données. Le patch terminé, je l'ai envoyé sur pgsql-hackers pour qu'il puisse être testé, relu et enfin commité. Je l'ai même saisi sur le site commitfest. Robert Haas s'en est occupé et l'a finalement commité vendredi sur toutes les versions, de la 8.0 (version à laquelle les tablespaces ont été ajoutées) à la future 9.0.

Nouvelles hebdomadaires de PostgreSQL - 27 juin 2010

2010-07-01T23:31:05+00:00

PostgreSQL est à la recherche de citations/témoignages pour la publication de la version 9.0. Si vous attendez avec impatience une ou plusieurs des fonctionnalités de la 9.0, et que vous représentez une entreprise ou une organisation gouvernementale ou non, envoyez-nous s'il vous plait votre participation à josh@postgresql.org.

PGXN, le "PostgreSQL Extension Network", inspiré du CPAN, a été lancé : http://www.pgxn.org/

Les nouveautés des produits dérivés

Slony-I 2.0.4, un système de réplication-en-cascade-maître-à-multiples-esclaves pour PostgreSQL : http://www.slony.info/
Benetl 3.5, un outil d'ETL pour PostgreSQL, spécialisé dans les fichiers : http://www.benetl.net
Muldis-D 0.130.0, une spécification pour un langage objet-relationnel prévu pour utiliser, entre autres systèmes, PostgreSQL : http://muldis.com/Muldis_D.html

Offres d'emplois autour de PostgreSQL en juin

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

PostgreSQL Local

CHAR(10), la conférence PostgreSQL dédiée au clustering, à la haute-disponibilité et à la réplication vient d'ouvrir les inscriptions en ligne et les réservations. 2 & 3 juillet 2010, Oriel College, Université d'Oxford (Royaume-Uni) : http://www.char10.org/
Le PDXPUG Day est programmé pour le 18 juillet 2010 à "l'Oregon Convention Center" à Portland. D'avantage d'informations : http://wiki.postgresql.org/wiki/PDXPUGDay2010
L'OSCON aura lieu à Portland (Oregon) du 19 au 23 juillet 2010 : http://www.oscon.com/oscon2010
La FrOSCon 2010 aura lieu à St. Augustin, Allemagne les 21 & 22 août 2010. Le PUG allemand a obtenu sa propre salle de dev. et est à la recherche de conférenciers. Plus de détails : http://andreas.scherbaum.la/blog/archives/711-FrOSCon-2010-PostgreSQL-devroom-Call-for-papers.html

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.

(lien vers l'article original)

Correctifs appliqués

Heikki Linnakangas a commité :

In pgsql/src/pl/plpgsql/src/pl_exec.c, in a PL/pgSQL "FOR cursor" statement, the statements executed in the loop might close the cursor, rendering the Portal pointer to it invalid. Closing the cursor in the middle of the loop is not a very sensible thing to do, but we must handle it gracefully and throw an error instead of crashing.

Robert Haas a commité :

Minor markup improvements for Hot Standby documentation.
Deprecate the use of => as an operator name. In HEAD, emit a warning when an operator named => is defined. In both HEAD and the backbranches (except in 8.2, where contrib modules do not have documentation), document that hstore's text => text operator may be removed in a future release, and encourage the use of the hstore(text, text) function instead. This function only exists in HEAD (previously, it was called tconvert), so backpatch it back to 8.2, when hstore was added. Per discussion.
In pgsql/contrib/hstore/expected/hstore.out, updated expected-output file for hstore. This is an oversight in my previous patch to deprecate => as an operator name. Per buildfarm.
Add TCP keepalive support to libpq. This adds four additional connection parameters to libpq: keepalives, keepalives_idle, keepalives_count, and keepalives_interval. keepalives default to on, per discussion, but can be turned off by specifying keepalives=0. The remaining parameters, where supported, can be used to adjust how often keepalives are sent and how many can be lost before the connection is broken. The immediate motivation for this patch is to make sure that walreceiver will eventually notice if the master reboots without closing the connection cleanly, but it should be helpful in other cases as well. Tollef Fog Heen, Fujii Masao, and me.
In pgsql/src/backend/postmaster/postmaster.c, add stray "else" that seems to have gone missing.
In pgsql/doc/src/sgml/release-9.0.sgml, further 9.0 release notes updates. Josh Berkus.
In pgsql/doc/src/sgml/high-availability.sgml, some copy-editing of the Hot Standby documentation. Thanks to Joshua Tolley for the review.
In pgsql/doc/src/sgml/installation.sgml, make AIX suggestions about disabling ipv6 more version-sensitive. Chris Browne, based on a report from John Pierce.
In pgsql/doc/src/sgml/libpq.sgml, rewrite docs for new libpq keepalive parameters. The revised documentation makes it more clear that these are client-side parameters, rather than server side parameters. It also puts the main point of each parameter first, and consolidates the conditions under which it might be ignored in a single list at the end.

Bruce Momjian a commité :

In pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml, update pg_ctl docs to explain server output behavior differences on win32 and non-win32 platforms.
Fix pg_upgrade's use of pg_ctl on Win32 to not send command and sever output to the same file, because it is impossible. Also set user name for pg_dumpall in pg_upgrade.
Add username designations to all pg_upgrade utility calls that support it.
In pgsql/doc/src/sgml/ref/alter_table.sgml, mention that when alter rewrites a table, indexes are also rebuilt.

Simon Riggs a commité :

Fix log_temp_files docs and comments to say bytes not kilobytes. stat(2) field st_size returns bytes not kilobytes. Bug found during recent performance tuning for PostgreSQL user.

Tom Lane a commité :

Fix thinko in tok_is_keyword(): it was looking at the wrong union variant of YYSTYPE, and hence returning the wrong answer for cases where a plpgsql "unreserved keyword" really does conflict with a variable name. Obviously I didn't test this enough :-(. Per bug #5524 from Peter Gagarinov.
In pgsql/src/bin/pg_dump/pg_backup_custom.c, fix pg_restore so parallel restore doesn't fail when the input file doesn't contain data offsets (which it won't, if pg_dump thought its output wasn't seekable). To do that, remove an unnecessarily aggressive error check, and instead fail if we get to the end of the archive without finding the desired data item. Also improve the error message to be more specific about the cause of the problem. Per discussion of recent report from Igor Neyman. Back-patch to 8.4 where parallel restore was introduced.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

Guillaume Lelarge sent in a patch to add a CHECK_FOR_INTERRUPTS call to the copy_relation_data(), copy_dir(), and copy_file() functions, which fixes an issue where cancelling ALTER TABLE ... SET TABLESPACE and ALTER DATABASE ... SET TABLESPACE did not work.
Heikki Linnakangas sent in a patch to fix an issue where the server would crash while trying to read an expression using pg_get_expr().
Andrew Dunstan sent in a WIP patch to make ENUMs alterable.
Kevin Grittner sent in a cleaned-up version of the patch to allow dividing money by money.
Peter Eisentraut sent in a patch to make PostgreSQL compile under clang.
Peter Eisentraut sent in another revision of the patch which allows ommission of non-aggregate columns in certain situations in GROUP BY.
Pavel Baros sent in a patch to implement materialized views.
Robert Haas sent in a patch to simplify emode_for_corrupt_record.
Mark Fowler sent in another revision of the patch to add an xpath_exists function.
Mark Fowler sent in another revision of the patch to add XMLEXISTS to the grammar.
Robert Haas sent in a patch to allow suppressing crash recovery after a crash, per discussion on -performance about a volatile version of PostgreSQL.

Vous voulez connaître les nouveautés de la 9.0 ?

2010-06-26T21:44:00+00:00

Alors allez lire le document rédigé par Marc Cousin. Il existe en version française et en version anglaise. Josh Berkus semble l'avoir beaucoup apprécié.. Et avec raison, car ce document est une mine.

Nouvelles hebdomadaires de PostgreSQL - 20 juin 2010

2010-06-24T22:07:28+00:00

Offres d'emplois autour de PostgreSQL en juin

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

PostgreSQL Local

Conférence de Michael Renner au Netways OSDC à Nuremberg (All.) les 23 & 24 juin 2010 : http://www.netways.de/osdc/y2010/programm/
CHAR(10), la conférence PostgreSQL dédiée au clustering, à la haute-disponibilité et à la réplication vient d'ouvrir les inscriptions en ligne et les réservations. 2 & 3 juillet 2010, Oriel College, Université d'Oxford (Royaume-Uni) : http://www.char10.org/
Le PDXPUG Day est programmé pour le 18 juillet 2010 à "l'Oregon Convention Center" à Portland. D'avantage d'informations : http://wiki.postgresql.org/wiki/PDXPUGDay2010
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.

(lien vers l'article original)

Correctifs appliqués

Heikki Linnakangas a commité :

In pgsql/src/backend/access/transam/xlog.c, if a corrupt WAL record is received by streaming replication, disconnect and retry. If the record is genuinely corrupt in the master database, there's little hope of recovering, but it's better than simply retrying to apply the corrupt WAL record in a tight loop without even trying to retransmit it, which is what we used to do.

ITAGAKI Takahiro a commité :

In pgsql/src/bin/psql/po/ja.po, fix typo in Japanese translation for psql "Use \d+ to list them."
Add new GUC categories corresponding to sections in docs, and move description for vacuum_defer_cleanup_age to the correct category. Sections in postgresql.conf are also sorted in the same order with docs. Per gripe by Fujii Masao, suggestion by Heikki Linnakangas, and patch by me.
In pgsql/src/include/replication/walsender.h, remove prototype of GetOldestWALSendPointer(), that is marked as NOT_USED.

Simon Riggs a commité :

In pgsql/contrib/Makefile, new contrib module for use as an archive_cleanup_command, or as a standalone utility for removing files from archive.
Files for pg_archivecleanup.
Docs for pg_archivecleanup.

Bruce Momjian a commité :

In pgsql/doc/src/sgml/plperl.sgml, fix doc plperl doc with is -> are change.
Properly define pg_upgrade global variable, per bug report from Chris Ruprecht on Mac (64 bit).
In pgsql/doc/src/sgml/ref/select.sgml, clarify SELECT FOR UPDATE behavior in docs.
In pgsql/contrib/pg_upgrade/option.c, fix storage of getopt() return, should be 'int', for pg_upgrade. Steve Singer.
In pgsql/doc/src/sgml/release-9.0.sgml, 9.0 release notes updates. Josh Berkus
In pgsql/doc/src/sgml/release-9.0.sgml, update doc description for 9.0 release note item: Have SELECT and CREATE TABLE AS return row counts to the client
In pgsql/contrib/pg_upgrade/tablespace.c, fix pg_upgrade to remove malloc(0) call.

Tom Lane a commité :

In pgsql/contrib/dblink/dblink.c, rearrange dblink's dblink_build_sql_insert() and related routines to open and lock the target relation just once per SQL function call. The original coding obtained and released lock several times per call. Aside from saving a not-insignificant number of cycles, this eliminates possible race conditions if someone tries to modify the relation's schema concurrently. Also centralize locking and permission-checking logic. Problem noted while investigating a trouble report from Robert Voinea --- his problem is still to be fixed, though.
Consolidate and improve checking of key-column-attnum arguments for dblink_build_sql_insert() and related functions. In particular, be sure to reject references to dropped and out-of-range column numbers. The numbers are still interpreted as physical column numbers, though, for backward compatibility. This patch replaces Joe Conway's patch of 2010-02-03, which handled only some aspects of the problem.
Fix dblink_build_sql_insert() and related functions to handle dropped columns correctly. In passing, get rid of some dead logic in the underlying get_sql_insert() etc functions --- there is no caller that will pass null value-arrays to them. Per bug report from Robert Voinea.
Change the interpretation of the primary_key_attnums parameter of dblink_build_sql_insert() and related functions. Now the column numbers are treated as logical not physical column numbers. This will provide saner behavior in the presence of dropped columns; furthermore, if we ever get around to allowing rearrangement of logical column ordering, the original definition would become nearly untenable from a usability standpoint. Per recent discussion of dblink's handling of dropped columns. Not back-patched for fear of breaking existing applications.
In pgsql/doc/src/sgml/libpq.sgml, fix typo, init => int, per KOIZUMI Satoru.
Don't allow walsender to send WAL data until it's been safely fsync'd on the master. Otherwise a subsequent crash could cause the master to lose WAL that has already been applied on the slave, resulting in the slave being out of sync and soon corrupt. Per recent discussion and an example from Robert Haas. Fujii Masao.
In pgsql/doc/src/sgml/ref/copy.sgml, add missing close brackets in old-style COPY syntax diagram. Spotted by Evan Carroll.
In pgsql/contrib/pg_archivecleanup/pg_archivecleanup.c, clean up pg_archivecleanup's error and logging output: put newlines in sane places, make messages follow project's message style guidelines. Also, avoid closedir(NULL). Fujii Masao and Tom Lane
In pgsql/src/backend/access/transam/xlog.c, make RemoveOldXlogFiles's debug printout match style used elsewhere: log and seg aren't an XLogRecPtr and shouldn't be printed like one. Fujii Masao.
Clean up some randomness associated with trace_recovery_messages: don't put the variable declaration in the middle of a bunch of externs, and do use extern where it should be used.
Fix mishandling of whole-row Vars referencing a view or sub-select. If such a Var appeared within a nested sub-select, we failed to translate it correctly during pullup of the view, because the recursive call to replace_rte_variables_mutator was looking for the wrong sublevels_up value. Bug was introduced during the addition of the PlaceHolderVar mechanism. Per bug #5514 from Marcos Castedo.

Andrew Dunstan a commité :

In pgsql/src/tools/msvc/Mkvcbuild.pm, unbreak MSVC builds for pg_archivecleanup by linking with libpgport.
Remove perl symbol table additions for plperl functions, and mention of it in the release notes, as it is not apparently providing anything useful.

Robert Haas a commité :

In pgsql/doc/src/sgml/ref/analyze.sgml, document new 9.0 behavior of ANALYZE on inheritance hierarchies. In particular, note that autovacuum does not yet understand that it might need to vacuum inheritance parents as a result of changes to the child tables.
Remove hstore's text[] => text[] operator. This is not yet in any released version, so we still have the option to backtrack. Instead, document hstore(text[], text[]). Per discussion.
In pgsql/doc/src/sgml/func.sgml, document that receive location can rewind if replication restarts. Fujii Masao, with some further wordsmithing by me.

Peter Eisentraut a commité :

Refactor sprintf calls with computed format strings into multiple calls with constant format strings, so that the compiler can more easily check the formats for correctness.
Add notes that CREATE/DROP CONVERSION is similar to CREATE/DROP TRANSLATION in the SQL standard.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

Robert Haas sent in a patch to implement --quote-all-identifiers for pg_dump and pg_dumpall, per discussion.
KaiGai Kohei sent in two revisions of a patch to add a security hook to InitPostgres().
KaiGai Kohei sent in a patch to rework DML permissions checks.
KaiGai Kohei sent in a patch to add makeRangeTblEntry into makefuncs.c.
KaiGai Kohei sent in a patch to modify the ExecutorCheckPerms() hook.
Fujii Masao sent in a patch to fix a condition where the server crashes during streaming replication.
Dimitri Fontaine sent in a patch to add a pg_archive_bypass command.
Robert Haas sent in another patch for get_whatever_oid.
Mike Lewis sent in another revision of the patch to enhance performance in array utility functions.
ITAGAKI Takahiro sent in a patch to reorganize GUC categories.
ITAGAKI Takahiro sent in a patch to implement foreign tables for SQL/MED.
Robert Haas sent in a patch to turn => into & for hstore.
Florian Pflug sent in a patch to show individual statement latencies in pgbench output.
Zoltan Boszormenyi sent in a patch to fix a performance problem in ECPG.
ITAGAKI Takahiro sent in an update revision of the patch for table partitioning syntax.
ITAGAKI Takahiro sent in a patch to add a view to pg_catalog for walsender activity.

Présentation de la version 9.0 de PostgreSQL

2010-06-21T12:08:07+00:00

Ce document tente de présenter les principaux changements apportés par PostgreSQL 9.0, par rapport à la version majeure précédente, la version 8.4. Dans la mesure du possible, chaque fonctionnalité sera expliquée et accompagnée d'une démonstration. Toutes les nouveautés ne sont bien sûr pas présentées (il y en a plus de 200).

La version 9.0, comme son nom l'indique, est une version capitale dans la progression de PostgreSQL. Même si les solutions de réplication pour PostgreSQL sont nombreuses et répondent à des problématiques variées, la version 9.0 apporte une réplication simple, robuste et intégrée au moteur, qui sera vraisemblablement utilisée par défaut dans la plupart des configurations de Haute Disponibilité reposant sur PostgreSQL.

Les changements ont été subdivisés en quatre parties:

Les deux nouveautés incontournables
Les nouveautés
Les changements pouvant entraîner des régressions
Les améliorations

Les incontournables

Ces deux nouveautés sont celles qui ont justifié à elles seules le renommage de 8.5 en 9.0.

Hot Standby

Cette nouvelle fonctionnalité est une des deux raisons du renommage en 9.0. Il s'agit de proposer une base de 'Standby', c'est-à-dire une baseappliquant les journaux binaires générés par la base de production, tout en la rendant ouverte en lecture seule. Ceci est assez complexe car, pendant l'exécution de ces requêtes en lecture seule, la base en Standby doit aussi pouvoir appliquer les données binaires provenant de la base de production, être capable de décider si les modifications peuvent entrer en conflit avec les lectures et déterminer les actions à entreprendre en conséquence : mettre en pause la restauration ou tuer des requêtes en lecture seule. Ce patch est volumineux et complexe, il rajoute des informations dans la journalisation à l'intention de la base de Standby et un mécanisme de résolution des conflits. C'est donc une des fonctionnalités majeures, et une des principales fonctionnalités à aider à tester.

Pour mettre ceci en place, il suffit de paramétrer la base de production comme suit :

postgresql.conf Primaire:

wal_level = 'hot standby' # Génère les informations supplémentaires dans les journaux
# vacuum_defer_cleanup_age # Optionnellement, vous pourriez vouloir paramétrer ceci, mais son réglage pourrait être complexe

Ensuite, créer une base de standby (la procédure est la même que précédemment pour un Warm Standby : pg_start_backup sur la production, recopie des fichiers sur l'esclave, pg_end_backup sur la production).

Puis il suffit de recopier les journaux sur le secondaire et de rajouter ceci dans son postgresql.conf :

postgresql.conf Secondaire:

hot_standby=on
max_standby_delay=30s # -1= toujours attendre, 0= ne jamais attendre, sinon attendre cette durée

et d'utiliser un programme comme pg_standby sur le secondaire pour intégrer les journaux (à paramétrer dans le recovery.conf).

max_standby_delay permet de déterminer le comportement de la base de standby en cas de conflit entre l'application des journaux de transactions et les requêtes en lecture seule. En cas de conflit, la base de standby acceptera d'attendre au plus max_standby_delay avant de tuer les requêtes en lecture qui bloquent l'application des journaux.

Il est bien sûr vivement conseillé de lire la documentation avant de mettre en place cette fonctionnalité… Ne serait-ce que pour bien comprendre les conséquences du réglage de max_standby_delay et vacuum_defer_cleanup_age, qui ne sont pas simples à appréhender.

Streaming Replication

C'est la deuxième moitié de la raison du passage en 9.0. Il s'agit cette fois-ci de modifier le mécanisme d'archivage pour le rendre continu : les bases de standby peuvent donc se connecter au maître et récupérer à tout moment ce qui leur manque des journaux, non plus en termes de fichiers entiers, mais bien en termes d'enregistrements dans ces journaux (des fragments de ces fichiers donc). Il s'agit donc bien d'une réplication binaire, pas de la rééxécution dans le même ordre de requêtes SQL comme sur certains autres moteurs de bases de données, avec tous les risques de cohérence que cela impliquerait.

Les bases de production et de standby sont identiques au niveau binaire (enfin presque, on ne va pas rentrer dans les détails, mais ne vous en faites pas si les fichiers de données n'ont pas la même somme de contrôle).

wal_level devra valoir « archive » (ou « hot standby ») pour continuer à faire de l'archivage continu.

postgresql.conf primaire :

max_wal_senders = x # Nombre maximum de « wal_senders », les processus chargés de répondre à des serveurs de standby
wal_keep_segments # Nombre de fichiers de journaux de transactions à conserver en ligne quoi qu'il arrive (évite d'avoir à les recopier manuellement sur le(s) secondaires en cas de déconnection lente)

Sur le secondaire :

recovery.conf secondaire:

stanby_mode = on
primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' # La chaîne de connexion pour une session sur le maître

postgresql.conf secondaire:

wal_level # à la même valeur que sur le maître (pour le retour de bascule…)
hot_standby=on/off # Suivant que vous voulez en même temps être en hot standby

fichier pg_hba.conf : On doit y créer une entrée pour les connexions de réplication. La base est « replication », l'utilisateur utilisé doit avoir l'attribut de superutilisateur. Attention à ne pas donner des droits trop importants ici, donner accès aux journaux de transactions en lecture à n'importe qui donne accès à des informations privilégiées.

pg_hba.conf primaire:

host    replication     foo             192.168.1.100/32        md5

Comme pour Hot Standby, cette fonctionnalité est suffisamment riche et complexe pour qu'il soit vivement conseillé de lire la doc. Et de faire des tests de bascule une fois l'ensemble mis en place.

Ce qui est très important avec ces deux fonctionnalités, c'est que vous pouvez les utiliser ensemble. Vous pouvez donc avoir donc une base de stanby répliquée de façon quasi-synchrone avec la production, et exécuter des requêtes en lecture seule sur cette base.

Les nouveautés

Contraintes d'exclusion

Il est maintenant possible de déclarer des contraintes d'unicité plus complexes que celles s'appuyant sur l'opérateur '=' (contrainte d'unicité, deux jeux de colonnes ne pouvant être identiques).

Nous allons, pour l'illustrer, utiliser l'exemple de l'auteur, en utilisant le type 'temporal' qu'il a aussi développé. Ce type de données permet de définir des 'plages de temps', c'est à dire par exemple 'la plage de 12h15 à 13h15'.

Il faut donc récupérer le module temporal à l'adresse suivante : http://pgfoundry.org/projects/temporal/ , le compiler et l'installer comme un contrib (exécuter le script SQL fourni).

CREATE TABLE reservation
(
  salle      TEXT,
  professeur TEXT,
  durant    PERIOD);

ALTER TABLE reservation ADD CONSTRAINT test_exclude EXCLUDE   USING gist (salle WITH =,durant WITH &&);

Par ceci, nous disons qu'un enregistrement doit être refusé (contrainte d'exclusion) s'il en existe déjà un vérifiant les deux conditions concerner la même salle, et être en intersection au niveau de l'intervalle de temps.

marc=# INSERT INTO reservation (professeur,salle,durant) VALUES ( 'marc', 'salle techno', period('2010-06-16 09:00:00', '2010-06-16 10:00:00'));
INSERT 0 1
marc=# INSERT INTO reservation (professeur,salle,durant) VALUES ( 'jean', 'salle chimie', period('2010-06-16 09:00:00', '2010-06-16 11:00:00'));
INSERT 0 1
marc=# INSERT INTO reservation (professor,room,during) VALUES ( 'marc', 'salle chimie', period('2010-06-16 10:00:00', '2010-06-16 11:00:00'));
ERROR:  conflicting key value violates exclusion constraint "test_exclude"
DETAIL:  Key (room, during)=(salle chimie, [2010-06-16 10:00:00+02, 2010-06-16 11:00:00+02)) conflicts with existing key (room, during)=(salle chimie, [2010-06-16 09:00:00+02, 2010-06-16 11:00:00+02)).

L'insertion est interdite, puisque la salle de chimie est déjà prise de 9h à 11h.

Triggers par colonne

Voici d'abord un trigger par colonne.

CREATE TRIGGER toto BEFORE UPDATE of a ON t1 FOR EACH ROW EXECUTE PROCEDURE mon_trigger();

Ce trigger ne se déclenche que si la colonne a de la table t1 a été modifiée.

Triggers WHEN

Voici maintenant des exemples tirés de la documentation officielle pour la clause WHEN des triggers:

CREATE TRIGGER check_update
BEFORE UPDATE ON accounts
FOR EACH ROW
WHEN (OLD.balance IS DISTINCT FROM NEW.balance)
EXECUTE PROCEDURE check_account_update();

CREATE TRIGGER log_update
AFTER UPDATE ON accounts
FOR EACH ROW
WHEN (OLD.* IS DISTINCT FROM NEW.*)
EXECUTE PROCEDURE log_account_update();

DEFERRABLE UNIQUE CONSTRAINTS

Cette fonctionnalité aussi promet d'être pratique. Voici un exemple avec une clé primaire au lieu d'une simple clé unique, mais cela revient au même :

marc=# CREATE TABLE test (a int primary key);
marc=# INSERT INTO test values (1), (2);
marc=# UPDATE test set a = a+1;
ERROR:  duplicate key value violates unique constraint "test_pkey"
DETAIL:  Key (a)=(2) already exists.

Normal, mais dommage : à la fin de la transaction, mes données auraient été cohérentes. D'autant plus que si la table avait été triée physiquement par ordre descendant, ça passait ! En 8.4, il n'y avait pas d'échappatoire simple, il fallait trouver une astuce pour mettre à jour les enregistrements dans le bon ordre.

Nous pouvons maintenant faire ceci :

marc=# CREATE TABLE test (a int primary key deferrable);
marc=# INSERT INTO test values (2),(1);
marc=# UPDATE test set a = a+1;
ERROR:  duplicate key value violates unique constraint "test_pkey"
DETAIL:  Key (a)=(2) already exists.

Ah zut, ça ne marche pas.

En fait, je l'ai fait exprès : j'en profite pour faire un petit rappel sur les contraintes deferrable/deferred : une contrainte 'deferrable' PEUT être vérifiée en fin de transaction (elle est 'retardable'). Il faut toutefois dire à PostgreSQL expressément qu'on veut vraiment faire ce contrôle en fin de transaction.

On peut, pour la session en cours demander à passer toutes les contraintes en 'DEFERRED' :

marc=# SET CONSTRAINTS ALL DEFERRED;
SET CONSTRAINTS
marc=# UPDATE test set a = a+1;
UPDATE 2

Si on veut ne pas avoir à effectuer le SET CONSTRAINTS à chaque fois, il est aussi possible de déclarer la contrainte comme INITIALLY DEFERRED:

CREATE TABLE test (a int PRIMARY KEY DEFERRABLE INITIALLY DEFERRED);

Un autre rappel s'impose : les contraintes DEFERRED sont plus lentes que les contraintes IMMEDIATE. Par ailleurs, il faut bien stocker la liste des enregistrements à vérifier en fin de transaction quelque part, et cela consomme de la mémoire. Attention à ne pas le faire sur des millions d'enregistrements d'un coup. C'est la raison pour laquelle les contraintes 'DEFERRABLE' ne sont pas 'INITIALLY DEFERRED' par défaut.

Fonctions anonymes

Cette nouvelle fonctionnalité permet de créer des fonctions à usage unique. Elles seront très pratiques dans des scripts de livraison de version applicative par exemple. Voici une version un peu différente du GRANT SELECT ON ALL TABLES qui sera présenté plus loin dans ce document, qui donne le droit de sélection à tout un jeu de tables, en fonction du propriétaire des tables, et en ignorant deux schémas :

DO language plpgsql $$ 
DECLARE
vr record;

BEGIN

FOR vr IN SELECT tablename FROM pg_tables WHERE tableowner = 'marc' AND schemaname NOT IN ('pg_catalog','information_schema')
LOOP
  EXECUTE 'GRANT SELECT ON ' || vr.tablename || ' TO toto';
END LOOP;
END
$$
;

En 8.4, il aurait fallu créer une fonction (via CREATE FUNCTION), l'exécuter puis la supprimer (avec DROP FUNCTION). Le tout demandant d'avoir les droits pour ça. La 9.0 facilite donc ce type d'exécution rapide.

Paramètres nommés

La syntaxe retenue pour nommer les paramètres est la suivante:

CREATE FUNCTION test (a int, b text) RETURNS text AS $$
DECLARE
valeur text;
BEGIN
valeur := 'a vaut ' || a::text || ' et b vaut ' || b;
RETURN valeur;
END;
$$ LANGUAGE plpgsql;

Jusque là, on écrivait :

SELECT test(1,'toto');
test           
-------------------------
a vaut 1 et b vaut toto
(1 row)

Maintenant, on peut utiliser cette syntaxe explicite:

SELECT test( b:='toto', a:=1);
test           
-------------------------
a vaut 1 et b vaut toto
(1 row)

De nombreux langages permettent ce type de syntaxe d'appel de fonction, qui améliore fortement la lisibilité du code.

GRANT/REVOKE IN SCHEMA

C'est un problème idiot, et un peu frustrant, qui est déjà arrivé à beaucoup d'administrateurs de base de données : créer 400 tables, puis devoir attribuer des droits à un utilisateur sur ces 400 tables. Jusque là, on en était quitte pour créer un script. Plus maintenant :

GRANT SELECT ON ALL TABLES IN SCHEMA public TO toto;

Et la marche arrière :

REVOKE SELECT ON ALL TABLES IN SCHEMA public FROM toto;

Bien sûr, cette commande ne vaut que pour les tables en place au moment de la commande. Il faudra toujours faire de nouveaux GRANT pour les futures tables du schéma.

ALTER DEFAULT PRIVILEGES

Encore une commande permettant de gagner du temps dans la gestion des droits.

ALTER DEFAULT PRIVILEGES FOR ROLE marc GRANT SELECT ON TABLES TO PUBLIC ;
CREATE TABLE test_priv (a int);
\z test_priv
                             Access privileges
 Schema |    Name    | Type  | Access privileges | Column access privileges 
--------+------------+-------+-------------------+--------------------------
 public | test_priv  | table | =r/marc          +| 
        |            |       | marc=arwdDxt/marc |

Les informations sur les droits par défaut sont stockées dans pg_default_acl.

Les changements pouvant entraîner régression

Ces deux changements dans PL/pgSQL peuvent entraîner des régressions dans du code fonctionnant en 8.4. Si vous avez du code PL/pgSQL, vérifiez le avant de migrer en 9.0. Le moteur génère des erreurs à l'exécution, comme illustré ci-dessous.

PL/pgSQL : meilleur contrôle du nom des variables

marc=# DO LANGUAGE plpgsql
$$
DECLARE
a int;
BEGIN
SELECT a FROM test;
END
$$
ERROR:  column reference "a" is ambiguous
LINE 1: select a from test
DETAIL:  It could refer to either a PL/pgSQL variable or a table column.
QUERY:  select a from test
CONTEXT:  PL/pgSQL function "inline_code_block" line 4 at SQL statement

Si vous voulez modifier ce comportement, vous pouvez le faire globalement mais il est préférable de le faire par fonction, en exécutant une de ces commandes au début de votre fonction:

variable_conflict error        # mode par défaut
variable_conflict use_variable # choisir le nom de variable
variable_conflict use_column   # choisir le nom de colonne

Protection des mots réservés en PL/pgSQL

marc=# DO LANGUAGE plpgsql
$$
DECLARE
table int;
BEGIN
table :=table+1;
END
$$
;
ERROR:  syntax error at or near "table"
LINE 6: table :=table+1;
^
marc=# DO LANGUAGE plpgsql
$$
DECLARE
"table" int;
BEGIN
"table" :="table"+1;
END
$$
;
DO

Les améliorations

Le planificateur de requête a reçu un grand nombre d'améliorations dans cette version. Nous allons donc commencer par lui:

Join Removal

marc=# CREATE TABLE t1 (a int);
CREATE TABLE
marc=# CREATE TABLE t2 (b int);
CREATE TABLE
marc=# CREATE TABLE t3 (c int);
CREATE TABLE

On insère quelques données avec le generate_series…

marc=# EXPLAIN SELECT t1.a,t2.b from t1 join t2 on (t1.a=t2.b) left join t3 on (t1.a=t3.c);
                                  QUERY PLAN                                  
------------------------------------------------------------------------------
 Merge Right Join  (cost=506.24..6146.24 rows=345600 width=8)
   Merge Cond: (t3.c = t1.a)
   ->  Sort  (cost=168.75..174.75 rows=2400 width=4)
         Sort Key: t3.c
         ->  Seq Scan on t3  (cost=0.00..34.00 rows=2400 width=4)
   ->  Materialize  (cost=337.49..853.49 rows=28800 width=8)
         ->  Merge Join  (cost=337.49..781.49 rows=28800 width=8)
               Merge Cond: (t1.a = t2.b)
               ->  Sort  (cost=168.75..174.75 rows=2400 width=4)
                     Sort Key: t1.a
                     ->  Seq Scan on t1  (cost=0.00..34.00 rows=2400 width=4)
               ->  Sort  (cost=168.75..174.75 rows=2400 width=4)
                     Sort Key: t2.b
                     ->  Seq Scan on t2  (cost=0.00..34.00 rows=2400 width=4)

Pour l'instant, c'est normal, et on a le même comportement qu'en 8.4. Mais imaginons que sur la table t3, on ait une contrainte UNIQUE sur la colonne c. Dans ce cas, théoriquement, la jointure sur la table t3 ne sert à rien : le nombre d'enregistrements du résultat ne sera pas modifié, pas plus, bien sûr, que leur contenu. C'est lié au fait que la colonne est UNIQUE, que la jointure est un LEFT JOIN, et qu'aucune colonne de t3 n'est récupérée. Si la colonne n'était pas UNIQUE, la jointure pourrait augmenter le nombre d'enregistrements du résultat. Si ce n'était pas un LEFT JOIN, la jointure pourrait diminuer le nombre d'enregistrements du résultat.

En 9.0 :

marc=# ALTER TABLE t3 ADD UNIQUE (c);
NOTICE:  ALTER TABLE / ADD UNIQUE will create implicit index "t3_c_key" for table "t3"
ALTER TABLE
marc=# EXPLAIN SELECT t1.a,t2.b from t1 join t2 on (t1.a=t2.b) left join t3 on (t1.a=t3.c);
                            QUERY PLAN                            
------------------------------------------------------------------
 Merge Join  (cost=337.49..781.49 rows=28800 width=8)
   Merge Cond: (t1.a = t2.b)
   ->  Sort  (cost=168.75..174.75 rows=2400 width=4)
         Sort Key: t1.a
         ->  Seq Scan on t1  (cost=0.00..34.00 rows=2400 width=4)
   ->  Sort  (cost=168.75..174.75 rows=2400 width=4)
         Sort Key: t2.b
         ->  Seq Scan on t2  (cost=0.00..34.00 rows=2400 width=4)
(8 rows)

Cette optimisation devrait pouvoir être très rentable, entre autre quand les requêtes sont générées par un ORM (mapping objet-relationnel). Ces outils ont la fâcheuse tendance à exécuter des jointures inutiles. Ici on a réussi à diviser le coût estimé de la requête par 10.

C'est aussi une optimisation qui pourra être très utile pour les applications utilisant beaucoup de jointures et de vues imbriquées.

Cela constitue encore une raison supplémentaire de déclarer les contraintes dans la base : sans ces contraintes, impossible pour le moteur d'être sûr que ces réécritures sont possibles.

IS NOT NULL peut utiliser les index

Pour cette démonstration, nous allons comparer la version 8.4 et la 9.0 (la table que j'ai créée contient majoritairement des valeurs NULL) :

En 8.4 :

marc=# EXPLAIN ANALYZE SELECT max(a) from test;
QUERY PLAN                                                                   
------------------------------------------------------------------------------------------------------------------------------------------------
Result  (cost=0.03..0.04 rows=1 width=0) (actual time=281.320..281.321 rows=1 loops=1)
InitPlan 1 (returns $0)
  ->  Limit  (cost=0.00..0.03 rows=1 width=4) (actual time=281.311..281.313 rows=1 loops=1)
  ->  Index Scan Backward using idxa on test  (cost=0.00..29447.36 rows=1001000 width=4) (actual time=281.307..281.307 rows=1 loops=1)
Filter: (a IS NOT NULL)
Total runtime: 281.360 ms
(6 rows)

En 9.0 :

marc=# EXPLAIN ANALYZE SELECT max(a) from test;
QUERY PLAN                                                                 
--------------------------------------------------------------------------------------------------------------------------------------------
Result  (cost=0.08..0.09 rows=1 width=0) (actual time=0.100..0.102 rows=1 loops=1)
InitPlan 1 (returns $0)
  ->  Limit  (cost=0.00..0.08 rows=1 width=4) (actual time=0.092..0.093 rows=1 loops=1)
  ->  Index Scan Backward using idxa on test  (cost=0.00..84148.06 rows=1001164 width=4) (actual time=0.089..0.089 rows=1 loops=1)
Index Cond: (a IS NOT NULL)
Total runtime: 0.139 ms
(6 rows)

On constate que la 9.0 parcourt uniquement les clés non nulles de l'index (Index cond, au lieu d'un filtre à posteriori). Dans ce cas précis, le gain est très net.

Utilisation d'index pour générer des statistiques à la volée

Avant de commencer à expliquer la nouveauté, un petit rappel sur les histogrammes: PostgreSQL, comme d'autres moteurs de bases de données, utilise un optimiseur statistique. Cela signifie qu'au moment de la planification d'une requête il a (ou devrait) avoir une idée correcte de ce que chaque étape de la requête va lui ramener, en termes de nombres d'enregistrements. Pour cela, il utilise des statistiques, comme le nombre d'enregistrements de la table approximatif, sa taille, la corrélation physique entre valeurs voisines dans la table, les valeurs les plus fréquentes, et les histogrammes, qui permettent d'évaluer assez précisément le nombre d'enregistrements ramenés par une clause WHERE sur une colonne, suivant la valeur ou la plage demandée sur la clause WHERE.

Il arrive que les statistiques soient rapidement périmées, et donc posent problème, pour certains ordres SQL. Par exemple, une table de trace dans laquelle on insèrerait des enregistrements horodatés, et sur laquelle on voudrait presque toujours sélectionner les enregistrements des 5 dernières minutes.

Dans ce cas, il était impossible avant la 9.0 d'avoir des statistiques à jour. Maintenant, quand PostgreSQL détecte qu'une requête demande un «range scan» sur une valeur supérieure à la dernière valeur de l'histogramme (ou inférieure à la première valeur), c'est à dire la plus grande valeur connue au dernier calcul de statistiques, et que la colonne est indexée, il récupère le max (ou le min si c'est la première valeur) de cette colonne en interrogeant l'index AVANT d'exécuter la requête, afin d'obtenir des statistiques plus réalistes. Comme il utilise un index pour cela, il faut qu'un index existe, bien sûr.

Voici un exemple. La colonne "a" de la table test a déjà été remplie avec de nombreuses dates, antérieures. Elle a donc des statistiques à jour, avec des histogrammes lui donnant la répartition des valeurs de a.

Il est 13:37, et je n'ai encore rien inséré dans la table de date supérieure à 13:37.

marc=# EXPLAIN ANALYZE select * from test where a > '2010-06-03 13:37:00';
QUERY PLAN                                                  
--------------------------------------------------------------------------------------------------------------
Index Scan using idxtsta on test  (cost=0.00..8.30 rows=1 width=8) (actual time=0.007..0.007 rows=0 loops=1)
Index Cond: (a > '2010-06-03 13:37:00'::timestamp without time zone)
Total runtime: 0.027 ms
(3 rows)

Tout est donc normal. La borne supérieure de mon histogramme est 2010-06-03 13:36:16.830007 (l'information se trouve dans pg_stats). Il n'a aucun moyen d'évaluer le nombre d'enregistrements supérieurs à 13:37, et en 8.4, il aurait continué à estimer '1' tant qu'un analyze n'aura pas été passé.

marc=# DO LANGUAGE plpgsql
$$
DECLARE
i int;
BEGIN
FOR i IN 1..10000 LOOP

   INSERT INTO test VALUES (clock_timestamp());

END LOOP;
END
$$
;
DO

(Décidément, j'aime bien les DO).

Nous venons d'insérer 10000 dates supérieures à 13:37.

marc=# EXPLAIN ANALYZE SELECT * FROM test WHERE a > '2010-06-03 13:37:00';
QUERY PLAN                                                       
-----------------------------------------------------------------------------------------------------------------------
Index Scan using idxtsta on test  (cost=0.00..43.98 rows=1125 width=8) (actual time=0.012..13.590 rows=10000 loops=1)
Index Cond: (a > '2010-06-03 13:37:00'::timestamp without time zone)
Total runtime: 23.567 ms
(3 rows)

Le nombre d'enregistrements estimé n'est pas à 0 ou 1. Et pourtant les statistiques ne sont pas à jour :

marc=# SELECT last_autoanalyze FROM pg_stat_user_tables WHERE relname = 'test';
last_autoanalyze        
-------------------------------
2010-06-03 13:36:21.553477+02
(1 row)

Dans cet exemple, nous avons tout de même une erreur d'un facteur 10. Ce n'est pas si mal: sans cette optimisation, l'erreur aurait été d'un facteur 10 000. En tout cas, une erreur d'un facteur 10 nous donne de plus fortes chances de choisir un plan intelligent.

seq_page_cost/random_page_cost par tablespace

marc=# ALTER TABLESPACE pg_default SET ( random_page_cost = 10, seq_page_cost=5);
ALTER TABLESPACE

Nous venons de modifier random_page_cost et seq_page_cost pour tous les objets du tablespace pg_default. Quel peut être le cas d'utilisation ?

C'est pour le cas où vous avez des tablespaces de performances différentes : par exemple, vous avez quelques données essentielles sur un disque SSD, ou bien des données d'historique sur une vieille baie moins performante que la baie flambant neuf que vous avez décidé d'utiliser pour les données actives. Cela vous permet de signaler à PostgreSQL que tous vos tablespaces ne sont pas forcément équivalents en termes de performance. Cela ne s'applique, bien sûr, que sur de très grosses bases.

Permettre de forcer le nombre de valeurs distinctes d'une colonne

Ceci permet de forcer le nombre de valeurs différentes d'une colonne. Ce n'est pas à utiliser à la légère, mais uniquement quand l'ANALYZE sur la table n'arrive pas à obtenir une valeur raisonnable.

Voici comment procéder :

marc=# ALTER TABLE test ALTER COLUMN a SET (n_distinct = 2);
ALTER TABLE

Il faut repasser un ANALYZE pour que la modification soit prise en compte :

marc=# ANALYZE test;
ANALYZE

Essayons maintenant :

marc=# EXPLAIN SELECT distinct * from test;
QUERY PLAN                            
------------------------------------------------------------------
HashAggregate  (cost=6263.00..6263.02 rows=2 width=8)
->  Seq Scan on test  (cost=0.00..5338.00 rows=370000 width=8)
(2 rows)

C'est l'exemple même de ce qu'il ne faut pas faire : j'ai bien 370 000 valeurs distinctes dans ma table. Maintenant mes plans d'exécution seront très mauvais.

Si la valeur n_distinct est positive, il s'agit du nombre de valeurs distinctes. Si la valeure est négative (entre 0 et -1), il s'agit du coefficient multiplicateur par rapport au nombre d'enregistrements estimés de la table : par exemple -0.2 signifie qu'il y a 1 enregistrement distinct pour 5 enregistrements dans la table. 0 ramène le comportement à celui par défaut (c'est ANALYZE qui effectue la mesure).

Ne touchez à ceci que si vous êtes absolument sûr d'avoir correctement diagnostiqué votre problème. Sinon, vous pouvez être sûr d'empirer les performances.

De nombreuses autres fonctionnalités de la base ont été améliorées. En voici quelques exemples parmi les plus significatifs :

VACUUM FULL amélioré

La commande VACUUM FULL était jusque ici très lente. Cette commande permet de récupérer l'espace perdu dans une table, principalement quand la commande VACUUM n'a pas été passée très régulièrement. Ceci était du à son mode de fonctionnement : les enregistrements étaient lus et déplacés un par un d'un bloc de la table vers un bloc plus proche du début de la table. Une fois que la fin de la table était vide, l'enveloppe était réduite à sa taille minimale.

Le problème était donc que ce mécanisme était très inefficace : le déplacement des enregistrements un à un entraine beaucoup d'entrées/sorties aléatoires (non contigues). Par ailleurs, durant cette réorganisation, les index doivent être maintenus, ce qui rend l'opération encore plus couteuse, et fait qu'à la fin d'un vacuum full, les index sont fortement désorganisés. Il est d'ailleurs conseillé de réindexer une table juste après y avoir appliqué un VACUUM FULL.

La commande VACUUM FULL, dans cette nouvelle version, crée une nouvelle table à partir de la table actuelle, en y recopiant tous les enregistrements de façon séquentielle. Une fois tous les enregistrements recopiés, les index sont recréés, et l'ancienne table détruite.

Cette méthode présente l'avantage d'être très largement plus rapide. Toutefois, VACUUM FULL demande toujours un verrou complet sur la table durant le temps de son exécution. Le seul défaut de cette méthode par rapport à l'ancienne, c'est que pendant le temps de son exécution, le nouveau VACUUM FULL peut consommer jusqu'à 2 fois l'espace disque de la table, puisqu'il en crée une nouvelle version.

Mesurons maintenant le temps d'exécution suivant les deux méthodes. Dans les deux cas, on prépare le jeu de test comme suit (en 8.4 et en 9.0:)

marc=# CREATE TABLE test (a int);
CREATE TABLE
marc=# CREATE INDEX idxtsta on test (a);
CREATE INDEX
marc=# INSERT INTO test SELECT generate_series(1,1000000);
INSERT 0 1000000
marc=# DELETE FROM test where a%3=0;
DELETE 333333
marc=# VACUUM test;
VACUUM

En 8.4 :
marc=# \timing
Timing is on.
marc=# VACUUM FULL test;
VACUUM
Time: 6306,603 ms
marc=# REINDEX TABLE test ;
REINDEX
Time: 1799,998 ms

Soit environ 8 secondes.

En 9.0 :
marc=# \timing
Timing is on.
marc=# VACUUM FULL test;
VACUUM
Time: 2563,467 ms

Ça ne veut toujours pas dire que VACUUM FULL est une bonne idée en production. Si vous en avez besoin, c'est probablement que votre politique de VACUUM n'est pas appropriée.

64 bits sous windows.

Il y a maintenant une version 64 bits native pour Windows. Pour l'instant aucune mesure de performance n'a été effectuée (à ma connaissance) pour en connaître les gains : peut on maintenant dépasser la limite de shared_buffers aux alentours de 500Mo sous Windows sans dégradations de performances ?

PL/pgSQL par défaut

Vous n'aurez plus à ajouter le langage plpgsql dans chaque base où vous en avez besoin car il est installé par défaut.

Beaucoup d'améliorations sur les langages PL.

Beaucoup de langages ont vu leur support grandement amélioré, PLPerl par exemple. Consultez les release notes si vous voulez davantage de détails, les modifications étant nombreuses.

Mot clé ALIAS

Nous pouvons maintenant utiliser le mot clé ALIAS. Comme son nom l'indique, il permet de créer des alias de variables.

La syntaxe est « nouveau_nom ALIAS FOR ancien_nom ». Cela se place dans la section DECLARE d'un code PL/pgSQL.

C'est utilisable dans deux cas principalement :

pour donner des noms aux variables d'une fonction PL:

   monparam ALIAS FOR $0

pour renommer des variables qui pourraient être en conflit. Dans un trigger par exemple:

   nouvelle_valeur ALIAS FOR new

(on aurait risqué le conflit avec la variable new dans la fonction trigger).

Passage de message dans NOTIFY/pg_notify

On peut donc passer des messages dans NOTIFY. Voici la méthode:

On s'abonne dans la session 1 à la file d'attente « messagerie_instantanee »
Session 1 :
```
marc=# LISTEN messagerie_instantanee;
LISTEN
```

On envoie une notification dans la file d'attente « messagerie_instantanee » d'une autre session
Session 2 :
```
marc=# NOTIFY messagerie_instantanee, 'Vous avez reçu un popup';
NOTIFY
```

On vérifie le contenu de la file d'attente
Session 1 :

LISTEN
Asynchronous notification "messagerie_instantanee" with payload "Vous avez reçu un popup" received from server process with PID 5943.

On peut donc maintenant associer des messages (payloads) aux notifications, ce qui rend le mécanisme beaucoup plus puissant.

Signalons aussi la présence d'une nouvelle fonction pg_notify.

Le code de la session 2 peut donc être:

SELECT pg_notify('messagerie_instantanee','Vous avez reçu un popup');

Cela peut simplifier l'écriture, dans le cas d'un programme devant piloter de nombreuses files de messages.

get_bit et set_bit pour les bit strings

En voici un exemple très synthétique. Cet outil permet de manipuler les bits indépendamment dans un bit().


marc=# SELECT set_bit('1111'::bit(4),2,0);
 set_bit 
---------
 1101
(1 row)


marc=# SELECT get_bit('1101'::bit(4),2);
 get_bit 
---------
       0
(1 row)

application_name pour pg_stat_activity

Dans la session de supervision :

marc=# SELECT * from pg_stat_activity where procpid= 5991;

datid | datname | procpid | usesysid | usename | application_name | client_addr | client_port |         backend_start         | xact_start | query_start | waiting | current_query
------+---------+---------+----------+---------+------------------+-------------+-------------+-------------------------------+------------+-------------+---------+----------------
16384 | marc    |    5991 |       10 | marc    | psql             |             |          -1 | 2010-05-16 13:48:10.154113+02 |            |             | f       | <IDLE>

(1 row)

Dans la session '5991' :

marc=# SET application_name TO 'mon_appli'; SET

Dans la session de supervision :

marc=# SELECT * from pg_stat_activity where procpid= 5991;

datid | datname | procpid | usesysid | usename | application_name | client_addr | client_port |         backend_start         | xact_start |          query_start          | waiting | current_query
------+---------+---------+----------+---------+------------------+-------------+-------------+-------------------------------+------------+-------------+---------+----------------
16384 | marc    |    5991 |       10 | marc    | mon_appli        |             |          -1 | 2010-05-16 13:48:10.154113+02 |            | 2010-05-16 13:49:13.107413+02 | f       | <IDLE>

(1 row)

À vous de le positionner correctement dans votre application, ou vos sessions. Votre DBA vous dira merci, sachant enfin qui lance quoi sur son serveur facilement.

Configuration par base de données+rôle

marc=# ALTER ROLE marc IN database marc set log_statement to 'all';
ALTER ROLE

Pour savoir qui a quelles modifications de variables dans quels rôles de quelles bases de données, il y a une nouvelle commande psql :

marc=# \drds

         List of settings
role | database |     settings
-----+----------+-----------------
marc | marc     | log_statement=all

(1 row)

Il y a donc eu une modification du catalogue pour gérer cette nouvelle fonctionnalité :

Table "pg_catalog.pg_db_role_setting"

  Column    |  Type  | Modifier
------------+--------+----------
setdatabase | oid    | not null
setrole     | oid    | not null
setconfig   | text   |

Tracer les parametres modifiés lors d'un rechargement du postgresql.conf

Voici un exemple, lors de la modification du paramètre log_line_prefix :

LOG:  received SIGHUP, reloading configuration files
<%> LOG:  parameter "log_line_prefix" changed to "<%u%%%d> "

Nouvelles options de frame dans les fonctions de fenêtrage

Si vous ne vous connaissez pas les fonctions de fenêtrage, lisez la présentation de la 8.4 ici : Nouveautés PostgreSQL 8.4

Il y a donc des nouveautés dans le paramétrage du 'frame' des fonctions de fenêtrage. Soit la table suivante (faute de mieux…)

marc=# SELECT * FROM salaire ;
entite | personne  | salaire | date_embauche 
-------+-----------+---------+---------------
R&D    | marc      |  700.00 | 2010-02-15
Compta | etienne   |  800.00 | 2010-05-01
R&D    | maria     |  700.00 | 2009-01-01
R&D    | kevin     |  500.00 | 2009-05-01
R&D    | jean      | 1000.00 | 2008-07-01
R&D    | tom       | 1100.00 | 2005-01-01
Compta | stephanie |  850.00 | 2006-01-01

Voici un exemple de fonctions de fenêtrage, sans préciser le frame.

marc=# SELECT entite, personne, salaire, date_embauche, avg(salaire) OVER (PARTITION BY entite ORDER BY date_embauche) FROM salaire;
entite | personne  | salaire | date_embauche |          avg          
-------+-----------+---------+---------------+-----------------------
Compta | stephanie |  850.00 | 2006-01-01    |  850.0000000000000000
Compta | etienne   |  800.00 | 2010-05-01    |  825.0000000000000000
R&D    | tom       | 1100.00 | 2005-01-01    | 1100.0000000000000000
R&D    | jean      | 1000.00 | 2008-07-01    | 1050.0000000000000000
R&D    | maria     |  700.00 | 2009-01-01    |  933.3333333333333333
R&D    | kevin     |  500.00 | 2009-05-01    |  825.0000000000000000
R&D    | marc      |  700.00 | 2010-02-15    |  800.0000000000000000

Le frame est le groupe d'enregistrements sur lequel la fonctions de fenêtrage est appliquée. Évidemment, si on ne précise pas la frame, il met une valeur par défaut. Voici la même requête, écrite avec une frame explicite.

marc=# SELECT entite, personne, salaire, date_embauche, avg(salaire) OVER (PARTITION BY entite ORDER BY date_embauche RANGE BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW) FROM salaire;
entite | personne  | salaire | date_embauche |          avg          
-------+-----------+---------+---------------+-----------------------
Compta | stephanie |  850.00 | 2006-01-01    |  850.0000000000000000
Compta | etienne   |  800.00 | 2010-05-01    |  825.0000000000000000
R&D    | tom       | 1100.00 | 2005-01-01    | 1100.0000000000000000
R&D    | jean      | 1000.00 | 2008-07-01    | 1050.0000000000000000
R&D    | maria     |  700.00 | 2009-01-01    |  933.3333333333333333
R&D    | kevin     |  500.00 | 2009-05-01    |  825.0000000000000000
R&D    | marc      |  700.00 | 2010-02-15    |  800.0000000000000000

La frame est donc par 'range', entre le début du range et l'enregistrement courant (pas vraiment l'enregistrement courant en fait, mais laissons de côté les subtilités, allez lire la doc si vous voulez en savoir plus). On constate que la fonction de moyenne (avg) est appliquée entre le premier des enregistrements du frame (les enregistrements de la même entité) et l'enregistrement courant.

Première nouveauté : en 9.0, la frame peut se calculer entre l'enregistrement courant et la fin du groupe (au lieu d'entre le début du groupe et l'enregistrement courant):

marc=# SELECT entite, personne, salaire, date_embauche, avg(salaire)  OVER (PARTITION BY entite ORDER BY date_embauche RANGE BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING) FROM salaire;
entite | personne  | salaire | date_embauche |         avg          
-------+-----------+---------+---------------+----------------------
Compta | stephanie |  850.00 | 2006-01-01    | 825.0000000000000000
Compta | etienne   |  800.00 | 2010-05-01    | 800.0000000000000000
R&D    | tom       | 1100.00 | 2005-01-01    | 800.0000000000000000
R&D    | jean      | 1000.00 | 2008-07-01    | 725.0000000000000000
R&D    | maria     |  700.00 | 2009-01-01    | 633.3333333333333333
R&D    | kevin     |  500.00 | 2009-05-01    | 600.0000000000000000
R&D    | marc      |  700.00 | 2010-02-15    | 700.0000000000000000

Deuxième nouveauté, on peut calculer des frames sur les n enregistrements précédents et n enregistrements suivants. Aucun intérêt avec ce jeu de données, mais il faut bien que je vous donne un exemple :

marc=# SELECT entite, personne, salaire, date_embauche, avg(salaire)  OVER (PARTITION BY entite ORDER BY date_embauche RANGE ROWS BETWEEN 1 PRECEDING AND 1 FOLLOWING) FROM salaire;
entite | personne  | salaire | date_embauche |          avg          
-------+-----------+---------+---------------+-----------------------
Compta | stephanie |  850.00 | 2006-01-01    |  825.0000000000000000
Compta | etienne   |  800.00 | 2010-05-01    |  825.0000000000000000
R&D    | tom       | 1100.00 | 2005-01-01    | 1050.0000000000000000
R&D    | jean      | 1000.00 | 2008-07-01    |  933.3333333333333333
R&D    | maria     |  700.00 | 2009-01-01    |  733.3333333333333333
R&D    | kevin     |  500.00 | 2009-05-01    |  633.3333333333333333
R&D    | marc      |  700.00 | 2010-02-15    |  600.0000000000000000

On reste bien sûr sur le groupe (voir l'enregistrement de tom par exemple, l'enregistrement d'etienne ne rentre pas dans le calcul de sa moyenne).

Si on voulait la même requête que précédemment, mais avec des moyennes sur 3 enregistrements glissants, sans réinitialiser à chaque entité (toujours aucun intérêt pratique dans l'exemple).

marc=# SELECT entite, personne, salaire, date_embauche, avg(salaire) OVER (ORDER BY entite, date_embauche ROWS BETWEEN 1 PRECEDING AND 1 FOLLOWING) FROM salaire;
entite | personne  | salaire | date_embauche |         avg          
--------+-----------+---------+---------------+----------------------
Compta | stephanie |  850.00 | 2006-01-01    | 825.0000000000000000
Compta | etienne   |  800.00 | 2010-05-01    | 916.6666666666666667
R&D    | tom       | 1100.00 | 2005-01-01    | 966.6666666666666667
R&D    | jean      | 1000.00 | 2008-07-01    | 933.3333333333333333
R&D    | maria     |  700.00 | 2009-01-01    | 733.3333333333333333
R&D    | kevin     |  500.00 | 2009-05-01    | 633.3333333333333333
R&D    | marc      |  700.00 | 2010-02-15    | 600.0000000000000000

Bref, un outil à maîtriser d'urgence, si ce n'est pas déjà le cas (même si je n'ai pas été capable de vous donner un exemple décent).

Tris dans les aggrégations

Celle-ci est un peu subtile : le résultat de certaines fonctions d'aggrégation dépend de l'ordre dans lequel on leur fournit les données.

Il ne s'agit évidemment pas de count, avg, mais plutôt de array_agg, xml_agg, string_agg…

Ce qui va me permettre de vous présenter deux nouvelles fonctionnalités d'un coup, string_agg étant une nouveauté de la 9.0.

Reprenons la table salaire. Je voudrais la liste des employés, concaténés dans un seul champ, par entité. C'est pour stocker dans mon tableur.

marc=# SELECT entite,string_agg(personne,', ') FROM salaire GROUP BY entite;
entite |          string_agg           
-------+-------------------------------
Compta | etienne, stephanie
R&D    | marc, maria, kevin, jean, tom

C'est déjà bien. Mais j'aimerais bien les avoir par ordre alphabétique, parce que je ne sais pas écrire de macro dans mon tableur pour retrier les données.

marc=# SELECT entite,string_agg(personne,', ' ORDER BY personne) FROM salaire GROUP BY entite;
entite |          string_agg           
--------+-------------------------------
Compta | etienne, stephanie
R&D    | jean, kevin, marc, maria, tom

Il suffit donc de rajouter une clause de tri à l'intérieur de la fonction d'agrégat, sans virgule à la fin.

Amélioration des erreurs sur contrainte : message plus clair

En 8.4:

marc=# INSERT INTO test VALUES (1);
ERROR:  duplicate key value violates unique constraint "test_a_key"

En 9.0:

marc=# INSERT INTO test VALUES (1);
ERROR:  duplicate key value violates unique constraint "test_a_key"
DETAIL:  Key (a)=(1) already exists.

Cela devrait aider à trouver les causes des violations de contrainte.

Explain buffers/statistiques sur les hash, xml, json, yaml, nouvelle syntaxe optionnelle explain

Voici un EXPLAIN ANALYZE classique :

marc=# EXPLAIN ANALYZE SELECT a, sum(c) FROM pere JOIN fils ON (pere.a = fils.b) WHERE b BETWEEN 1000 AND 300000 GROUP BY a;                                                           QUERY PLAN                                                            
---------------------------------------------------------------------------------------------------------------------------------
 HashAggregate  (cost=905.48..905.86 rows=31 width=8) (actual time=0.444..0.453 rows=6 loops=1)
   ->  Nested Loop  (cost=10.70..905.32 rows=31 width=8) (actual time=0.104..0.423 rows=6 loops=1)
         ->  Bitmap Heap Scan on fils  (cost=10.70..295.78 rows=31 width=8) (actual time=0.040..0.154 rows=30 loops=1)
               Recheck Cond: ((b >= 1000) AND (b <= 300000))
               ->  Bitmap Index Scan on fils_pkey  (cost=0.00..10.69 rows=31 width=0) (actual time=0.023..0.023 rows=30 loops=1)
                     Index Cond: ((b >= 1000) AND (b <= 300000))
         ->  Index Scan using pere_pkey on pere  (cost=0.00..19.65 rows=1 width=4) (actual time=0.005..0.005 rows=0 loops=30)
               Index Cond: (pere.a = fils.b)
 Total runtime: 0.560 ms
(9 rows)

Si vous voulez avoir accès aux nouvelles informations, il faut opter pour la nouvelle syntaxe :

EXPLAIN [ ( { ANALYZE boolean | VERBOSE boolean | COSTS boolean | BUFFERS boolean | FORMAT { TEXT | XML | JSON | YAML } } [, ...] ) ] instruction

Par exemple :

marc=# EXPLAIN (ANALYZE true, VERBOSE true, BUFFERS true) SELECT a, sum(c) FROM pere JOIN fils ON (pere.a = fils.b) WHERE b BETWEEN 1000 AND 300000 GROUP BY a;
                                                             QUERY PLAN 
-------------------------------------------------------------------------------------------------------------------------------------
 HashAggregate  (cost=905.48..905.86 rows=31 width=8) (actual time=1.326..1.336 rows=6 loops=1)
   Output: pere.a, sum(fils.c)
   Buffers: shared hit=58 read=40
   ->  Nested Loop  (cost=10.70..905.32 rows=31 width=8) (actual time=0.278..1.288 rows=6 loops=1)
         Output: pere.a, fils.c
         Buffers: shared hit=58 read=40
         ->  Bitmap Heap Scan on public.fils  (cost=10.70..295.78 rows=31 width=8) (actual time=0.073..0.737 rows=30 loops=1)
               Output: fils.b, fils.c
               Recheck Cond: ((fils.b >= 1000) AND (fils.b <= 300000))
               Buffers: shared hit=4 read=28
               ->  Bitmap Index Scan on fils_pkey  (cost=0.00..10.69 rows=31 width=0) (actual time=0.030..0.030 rows=30 loops=1)
                     Index Cond: ((fils.b >= 1000) AND (fils.b <= 300000))
                     Buffers: shared hit=3
         ->  Index Scan using pere_pkey on public.pere  (cost=0.00..19.65 rows=1 width=4) (actual time=0.013..0.014 rows=0 loops=30)
               Output: pere.a
               Index Cond: (pere.a = fils.b)
               Buffers: shared hit=54 read=12
 Total runtime: 1.526 ms
(18 rows)

VERBOSE apporte les lignes 'Output' (l'option existait déjà en 8.4).

BUFFERS indique les opérations sur les buffers (les entrées sorties de la requête): hit correspond aux données lues en cache, read aux données demandées au système d'exploitation. Ici, peu de données étaient en cache.

Vous pouvez aussi demander une sortie dans un autre format que texte. Pour un utilisateur, cela n'a aucune importance. Pour les développeurs d'interfaces graphiques présentant le résultat d'explain, cela permettra de faire l'économie d'un analyseur sur le texte du EXPLAIN, et des bugs qui vont avec.

On peut aussi désactiver l'affichage des coûts avec COSTS false.

Dictionnaire de filtrage (unaccent)

Il est possible maintenant de paramétrer des dictionnaires de filtrage. On parle bien sûr des dictionnaires du Full Text Search.

Le but de ces dictionnaires de filtrage est d'appliquer un premier filtrage sur les mots avant de les indexer. Le module présenté ci-dessous (unaccent) est l'illustration de ce mécanisme. Le filtrage peut consister en la suppression de mots ou en leur modification.

Unaccent ne supprime pas les mots, il supprime les accents (tous les signes diacritiques en fait), en remplaçant les caractères accentués par leur version sans accent. Unaccent est un module contrib.

Pour l'installer, comme pour toutes les contribs, psql mabase < chemin_contribs/unaccent.sql.

Nous allons à peu près suivre la documentation d'unaccent, les auteurs ayant eu la gentillesse de donner leurs exemples en français.

Nous créons un nouveau dictionnaire fr (pour ne pas polluer le dictionnaire french 'standard') :

marc=# CREATE TEXT SEARCH CONFIGURATION fr ( COPY = french );
CREATE TEXT SEARCH CONFIGURATION

Nous modifions le paramétrage de 'fr' pour les lexemes de type mot, en lui demandant de les faire passer par unaccent et french_stem (au lieu de seulement french_stem)

marc=# ALTER TEXT SEARCH CONFIGURATION fr
ALTER MAPPING FOR hword, hword_part, word
WITH unaccent, french_stem;
ALTER TEXT SEARCH CONFIGURATION

SELECT to_tsvector('fr','Hôtels de la Mer');
to_tsvector    
-------------------
'hotel':1 'mer':4
(1 row)

marc=# SELECT to_tsvector('fr','Hôtel de la Mer') @@ to_tsquery('fr','Hotels');
?column? 
----------
t
(1 row)

Cela vous permet donc, sans changer une ligne de code, et en gardant les caractères accentués, de rechercher maintenant sans accent.

vacuumdb --analyze-only

Comme son nom l'indique, on peut maintenant utiliser vacuumdb pour passer des analyses uniquement. Cela peut être pratique dans une crontab.

Amélioration du module contrib hstore

Ce contrib, déjà très pratique, devient encore plus puissant :

La limite de taille sur les clés et valeurs a été supprimée.
Il est maintenant possible d'utiliser GROUP BY et DISTINCT
De nombreux opérateurs et fonctions ont été ajoutés

Un exemple serait trop long, tellement ce module est riche. Lisez la documentation sans perdre de temps !

Texte requête dans auto_explain

Le module contrib auto_explain affichera maintenant le code de la requête en même temps que son plan, ce qui devrait en augmenter la lisibilité.

Compteurs sur buffers dans pg_stat_statements

Ce module contrib, déjà très utile, vient de rajouter des compteurs. Pour rappel, son intérêt est de stocker des statistiques sur les requêtes exécutées par le moteur. Jusque là, il donnait la requête, le nombre d'exécutions, son temps cumulé et le nombre d'enregistrements cumulés. Maintenant, il collecte aussi des informations sur les entrées sorties (en cache, et réelles).

marc=# SELECT * from pg_stat_statements order by total_time desc limit 2;
-[ RECORD 1 ]-------+---------------------
userid              | 10
dbid                | 16485
query               | SELECT * from fils ;
calls               | 2
total_time          | 0.491229
rows                | 420000
shared_blks_hit     | 61
shared_blks_read    | 2251
shared_blks_written | 0
local_blks_hit      | 0
local_blks_read     | 0
local_blks_written  | 0
temp_blks_read      | 0
temp_blks_written   | 0
-[ RECORD 2 ]-------+---------------------
userid              | 10
dbid                | 16485
query               | SELECT * from pere;
calls               | 2
total_time          | 0.141445
rows                | 200000
shared_blks_hit     | 443
shared_blks_read    | 443
shared_blks_written | 0
local_blks_hit      | 0
local_blks_read     | 0
local_blks_written  | 0
temp_blks_read      | 0
temp_blks_written   | 0

On peut donc, une fois ce contrib installé, répondre aux questions suivantes :

Quelle est la requête la plus gourmande en temps d'exécution cumulé ?
Quelle est la requête qui génère le plus d'entrées sorties ? (attention, les données peuvent être tout de même dans le cache système)
Quelles requêtes utilisent principalement le cache (et ne gagneront donc pas à le voir augmenté)
Qui effectue beaucoup de mises à jour de bloc ?
Qui génère des tris ?

'local' et 'temp' correspondent aux buffers et entrées des tables temporaires et autres opérations locales (tris, hachages) à un backend.

passwordcheck

Ce module contrib permet de vérifier les mots de passe, et d'empêcher les plus mauvais de rentrer. Après l'avoir installé comme décrit dans la documentation, voici le résultat :

marc=# ALTER USER marc password 'marc12';
<marc%marc> ERROR:  password is too short
<marc%marc> STATEMENT:  ALTER USER marc password 'marc12';
ERROR:  password is too short
marc=# ALTER USER marc password 'marc123456';
<marc%marc> ERROR:  password must not contain user name
<marc%marc> STATEMENT:  ALTER USER marc password 'marc123456';
ERROR:  password must not contain user name

Ce module souffre de limitations, principalement dues au fait que PostgreSQL permet l'envoi d'un mot de passe déjà encrypté à la base au moment de la déclaration, ce qui l'empêche de le vérifier correctement. Néanmoins, c'est une avancée dans la bonne direction.

Par ailleurs, le code du module contrib est bien documenté, ce qui permet de l'adapter à vos besoins (entre autres, il est très facile d'y activer la cracklib, afin d'effectuer des contrôles plus complexes).

marc.cousin@dalibo.com

Créer ses propres types de données avec PostgreSQL

2010-06-21T00:00:00+00:00

Une des grands forces du SGBD PostgreSQL est la possibilité de créer ses propres types de données. Voici deux exemples complets et expliqués, un pour les nombres rationnels, l'autre pour les noms de domaine.

Fin de la traduction du manuel de la 9.0 (beta 2)

2010-06-17T18:06:00+00:00

Enfin, pour moi en tout cas. Il ne reste plus aucun fichier à réserver pour la traduction. Seuls quatre fichiers sont toujours à traduire mais déjà réservés. En attendant leur traduction, il est possible de lire le reste au format HTML ou au format PDF.

Bonne lecture.

Et n'hésitez pas à me faire parvenir tout problème de traduction.

Nouvelles hebdomadaires de PostgreSQL - 13 juin 2010

2010-06-15T21:39:47+00:00

PostgreSQL 9.0 beta 2 publiée. Testez ! http://www.postgresql.org/developer/beta

Nouveau sondage : laquelle des fonctionnalités de la 9.0 Beta (hors réplication) est votre préférée ? http://www.postgresql.org/community/

Les archives vidéo du rassemblement du SFPUG du 8 décembre 2009 : "Contraintes d'Exclusion via Opérateur", sont maintenant disponibles : http://thebuild.com/blog/2009/12/23/sfpug-operator-exclusion-constraints/

Les nouveautés des produits dérivés

pgnotifyd v0.1, un gestionnaire de notification asynchrone pour PostgreSQL : http://www.pogo.org.uk/~mark/pgnotifyd/

Offres d'emplois autour de PostgreSQL en juin

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

PostgreSQL Local

Conférence de Michael Renner au Netways OSDC à Nuremberg (All.) les 23 & 24 juin 2010 : http://www.netways.de/osdc/y2010/programm/
CHAR(10), la conférence PostgreSQL dédiée au clustering, à la haute-disponibilité et à la réplication vient d'ouvrir les inscriptions en ligne et les réservations. 2 & 3 juillet 2010, Oriel College, Université d'Oxford (Royaume-Uni) : http://www.char10.org/
Le PDXPUG Day est programmé pour le 18 juillet 2010 à "l'Oregon Convention Center" à Portland. D'avantage d'informations : http://wiki.postgresql.org/wiki/PDXPUGDay2010
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 et Josh Berkus. Traduction par l'équipe PostgreSQLFr sous licence CC BY-NC-SA.

(lien vers l'article original)

Correctifs appliqués

Teodor Sigaev a commité :

In pgsql/contrib/dblink/uninstall_dblink.sql, add missed function dblink_connect_u(text[,text]) to uninstall script

Tom Lane a commité :

In pgsql/src/backend/replication/walreceiver.c, avoid useless snprintf() call when update_process_title is turned off. Fujii Masao.
In pgsql/src/pl/plpython/plpython.c, fix quite-bogus handling of arrays in plpython datum-to-PyObject conversion. Per bug #5497 from David Gardner.
In pgsql/src/bin/scripts/vacuumdb.c, add missing 'Z' letter to getopt_long call --- the newly added --analyze-only switch did not work in its short form -Z. Josh Berkus
In pgsql/doc/src/sgml/Makefile, Postgres.txt should get cleaned by 'make clean'.

Robert Haas a commité :

In pgsql/doc/src/sgml/plhandler.sgml, make procedural language handler reference C-language function docs. Based on suggestions from Jonathan Leto and Joshua Tolley.
In pgsql/src/backend/commands/explain.c, attempt to fix EXPLAIN (FORMAT YAML) quoting to behave sanely. The previous code failed to quote in many cases where quoting was necessary - YAML has loads of special characters, including -:[]{},"'|*& - so quote much more aggressively, and only refrain from quoting things where it seems fairly clear that it isn't necessary. Per report from Dean Rasheed.
In pgsql/src/backend/catalog/pg_largeobject.c, remove stray word from comment.
In pgsql/src/backend/commands/explain.c, quote all string values in EXPLAIN (FORMAT YAML) output. While my previous attempt seems to always produce valid YAML, it doesn't always produce YAML that means what it appears to mean, because of tokens like "0xa" and "true", which without quotes will be interpreted as integer or Boolean literals. So, instead, just quote everything that's not known to be a number, as we do for JSON. Dean Rasheed, with some changes to the comments by me.
Fix ALTER LARGE OBJECT and GRANT ... ON LARGE OBJECT for large OIDs. The previous coding failed for OIDs too large to be represented by a signed integer.
In pgsql/doc/src/sgml/release-9.0.sgml, fix typo.
In pgsql/doc/src/sgml/release-9.0.sgml, fix misplaced modifier. As suggested by Ian Barwick.

Tatsuo Ishii a commité :

In pgsql/src/backend/replication/walreceiver.c, fix typo in the header comment. Per request from Masao Fujii.

ITAGAKI Takahiro a commité :

In pgsql/contrib/dblink/dblink.c, fix connection leak in dblink when dblink_connect() or dblink_connect_u() end with "duplicate connection name" errors. Backported to release 7.4.
In pgsql/contrib/dblink/dblink.c, avoid "identifier will be truncated" warning in dblink when connection string is longer than NAMEDATALEN. The previous fix for long connection name broke the behavior.
In pgsql/contrib/dblink/dblink.c, fix incorrect change in dblink introduced by the previous commit "Fix connection leak in dblink".
Rename restartpoint_command to archive_cleanup_command.
In pgsql/src/backend/storage/ipc/standby.c, remove max_standby_delay message from ps display of recovery process in waiting status. The parameter is not so interesting in ps display because it is referable in postgresql.conf.

Magnus Hagander a commité :

In pgsql/src/backend/access/transam/xlog.c, make the walwriter close its handle to an old xlog segment if it's no longer the current one. Not doing this would leave the walwriter with a handle to a deleted file if there was nothing for it to do for a long period of time, preventing the file from being completely removed. Reported by Tollef Fog Heen, and thanks to Heikki for some hand-holding with the patch.

Heikki Linnakangas a commité :

In standby mode, respect checkpoint_segments in addition to checkpoint_timeout to trigger restartpoints. We used to deliberately only do time-based restartpoints, because if checkpoint_segments is small we would spend time doing restartpoints more often than really necessary. But now that restartpoints are done in bgwriter, they're not as disruptive as they used to be. Secondly, because streaming replication stores the streamed WAL files in pg_xlog, we want to clean it up more often to avoid running out of disk space when checkpoint_timeout is large and checkpoint_segments small. Patch by Fujii Masao, with some minor changes by me.
Return NULL instead of 0/0 in pg_last_xlog_receive_location() and pg_last_xlog_replay_location(). Per Robert Haas's suggestion, after Itagaki Takahiro pointed out an issue in the docs. Also, some wording changes in the docs by me.
Make TriggerFile variable static. It's not used outside xlog.c. Fujii Masao.

Alvaro Herrera a commité :

In pgsql/doc/src/sgml/syntax.sgml, add index entry for ::, per complaint from John Gage.
In pgsql/doc/src/sgml/ref/alter_table.sgml, update ALTER TABLE docs to account for exclusion and deferrable uniqueness constraints. Dean Rasheed.

Bruce Momjian a commité :

In pgsql/doc/src/sgml/release-9.0.sgml, update text of 9.0 release notes. Josh Berkus.
In pgsql/doc/src/sgml/Makefile, add space between after ">" in ">$@" in SGML Makefile, for clarity.
In pgsql/doc/src/sgml/Makefile, add SGML Makefile rule for single-page text, postgres.txt.
Have pg_upgrade create its output files in the current directory, rather than in a subdirectory of the $HOME directory, or $TMP in Windows.
In pgsql/doc/src/sgml/Makefile, remove lynx -stdin flag for postgres.text.
In pgsql/src/test/regress/pg_regress.c, add missing --use-existing --help mention from regression binary. Jan Urbanski
In pgsql/contrib/pg_upgrade/pg_upgrade.h, update pg_upgrade C comment about cwd.

Peter Eisentraut a commité :

Add a regression test case for bug #5497.
In pgsql/src/pl/plpython/expected/README, update Python version information.
In pgsql/src/backend/access/transam/xlog.c, fix typo/bug, found by Clang compiler.
Add target to build HTML documentation as single page.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

Fujii Masao sent in a patch per Andrew Dunstan to clarify that to use a pgpass file to connect to Streaming Replica standbys, it is necessary to use a * for the database field.
Peter Eisentraut sent in a WIP patch to allow GROUP BY to infer functional dependencies and not require that the target list include all non-aggregated columns when it finds them, per the SQL standard.
Alexander Korotkov sent in another revision of the patch to allow multi-byte character sets in Levenshtein functions in the supplied module for fuzzy string matching.
Joel Jacobson sent in another revision of the patch to add a pg_stat_transaction system view.
Robert Haas sent in a patch to deprecate => and add ==> to the hstore module, per discussion.

Nouvelles hebdomadaires de PostgreSQL - 6 juin 2010

2010-06-12T22:44:20+00:00

Le 11 juin 2010, Gabriele Bartolini (de 2^ndQuadrant Italia) interviendra lors de la conférence italienne sur les Logiciels Libres à Cagliari, Sardaigne ; intervention titrée "High Availability of business databases with PostgreSQL" [ndt: Haute Disponibilité de bases de données d'entreprises avec PostgreSQL] : http://www.confsl.org/

Le 12 juin 2010, le PUG italien fera la promotion de PostgreSQL lors de la conférence italienne sur les Logiciels Libres à Cagliari, Sardaigne avec une journée entière d'ateliers autour de PostgreSQL allant d'une "Introduction" à la "Haute Disponibilité" : http://www.confsl.org/

Les nouveautés des produits dérivés

ChronicDB v2.2.2, un outil de déploiement de schéma : http://chronicdb.com

Offres d'emplois autour de PostgreSQL en juin

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

PostgreSQL Local

La "Southeast Linuxfest 2010" aura lieu à Spartanburg (Caroline du Sud, États-Unis) du 11 au 13 juin. Nos PG-gourous Joshua Drake et Andrew Dunstan donneront des présentations à ne pas manquer : http://southeastlinuxfest.org/
Conférence de Michael Renner au Netways OSDC à Nuremberg (All.) les 23 & 24 juin 2010 : http://www.netways.de/osdc/y2010/programm/
CHAR(10), la conférence PostgreSQL dédiée au clustering, à la haute-disponibilité et à la réplication vient d'ouvrir les inscriptions en ligne et les réservations. 2 & 3 juillet 2010, Oriel College, Université d'Oxford (Royaume-Uni) : http://www.char10.org/
Le PDXPUG Day est programmé pour le 18 juillet 2010 à "l'Oregon Convention Center" à Portland. D'avantage d'informations : http://wiki.postgresql.org/wiki/PDXPUGDay2010
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.

(lien vers l'article original)

Correctifs appliqués

Heikki Linnakangas a commité :

In pgsql/src/backend/replication/walsender.c, send all outstanding WAL before exiting when smart shutdown is requested. This was broken by my previous patch to send WAL in smaller batches. Patch by Fujii Masao.
In pgsql/src/backend/access/transam/xlog.c, fix obsolete comments that I neglected to update in a previous patch. Fujii Masao.

Bruce Momjian a commité :

In pgsql/doc/src/sgml/config.sgml, reword fsync and full_page_writes docs to be clearer about when to turn them off. Josh Berkus, with slight wording changes by me.
In pgsql/src/pl/plpgsql/src/pl_exec.c, add error hint that PL/pgSQL "EXECUTE of SELECT ... INTO" can be performed by "EXECUTE ... INTO". Jaime Casanova.
In pgsql/doc/src/sgml/docguide.sgml, document how to find TeX overflow boxes in our documentation build, per details from Alvaro Herrera.
In pgsql/doc/src/sgml/docguide.sgml, update TeX overflow documentation page pattern mask, in docs.
In pgsql/doc/src/sgml/docguide.sgml, overflow box is on page after listed page number, per Alvaro.
In pgsql/src/backend/commands/indexcmds.c, show schema name for REINDEX. Greg Sabino Mullane.
In pgsql/doc/src/sgml/extend.sgml, add documentation section "Using C++ for Extensibility". Craig Ringer
In pgsql/doc/src/sgml/extend.sgml, fix SGML markup for tag title.
In pgsql/doc/src/sgml/extend.sgml, mention palloc/pfree for C++ memory allocation in docs.
Comment out C++ docs for later user. Tone down C++ compatibility in 9.0 release notes.
In pgsql/doc/src/sgml/release-9.0.sgml, update C++ release note item wording.
In pgsql/doc/src/sgml/func.sgml, document that && geometric operator is true even if only a point overlaps. David Fetter.
In pgsql/doc/src/sgml/func.sgml, clarify array generate_subscripts() documentation example. Tim Landscheidt.
In pgsql/doc/src/sgml/citext.sgml, document that citext operators must be in the current search path.
In pgsql/doc/src/sgml/extend.sgml, document use of C++ for extension use.
In pgsql/doc/src/sgml/func.sgml, document regexp_matches() better and show example of single-row usage.
In pgsql/doc/src/sgml/extend.sgml, markup fix.
In pgsql/doc/src/sgml/release-9.0.sgml, update 9.0 release notes to current.
In pgsql/doc/src/sgml/release-9.0.sgml, fix CREATE TRIGGER release mention, WHERE -> WHEN.

Alvaro Herrera a commité :

In pgsql/doc/src/sgml/ref/reassign_owned.sgml, add note about database ownership to REASSIGN OWNED command documentation, per Josh Berkus. Add ALTER DATABASE to the "see also" section, too.
In pgsql/src/include/catalog/pg_control.h, add comments about definitions that may affect PG_CONTROL_VERSION, per recent unintended-initdb-forcing fiasco

Andrew Dunstan a commité :

In pgsql/src/tools/msvc/vcregress.pl, run recently backported plperlu_plperl regression tests when building with MSVC on releases 8.4 and 8.3. Regression tests weren't supported before that.
In pgsql/src/tools/msvc/vcregress.pl, fix regression test name for plperlu_plperl in msvc.

Robert Haas a commité :

On clean shutdown during recovery, don't warn about possible corruption. Fujii Masao. Review by Heikki Linnakangas and myself.

ITAGAKI Takahiro a commité :

In pgsql/contrib/dblink/dblink.c, fix dblink to treat connection names longer than NAMEDATALEN-2 (62 bytes). Now long names are adjusted with truncate_identifier() and NOTICE messages are raised if names are actually truncated. Backported to release 8.0.
Replace "slave" to "standby" in documentation for consistent terminology. Almost all of the terms in docs and messages were replaced, but still remains in a few comments and README files in codes.
Ensure default-only storage parameters for TOAST relations to be initialized with proper values. Affected parameters are fillfactor, analyze_threshold, and analyze_scale_factor. Especially uninitialized fillfactor caused inefficient page usage because we built a StdRdOptions struct in which fillfactor is zero if any reloption is set for the toast table. In addition, we disallow toast.autovacuum_analyze_threshold and toast.autovacuum_analyze_scale_factor because we didn't actually support them; they are always ignored. Report by Rumko on pgsql-bugs on 12 May 2010. Analysis by Tom Lane and Alvaro Herrera. Patch by me. Backpatch to 8.4.

Tom Lane a commité :

In pgsql/src/include/catalog/pg_control.h, bump PG_CONTROL_VERSION to account for the incompatible change committed earlier.
In pgsql/doc/src/sgml/release-9.0.sgml, remove link that breaks HISTORY file generation.
Add current WAL end (as seen by walsender, ie, GetWriteRecPtr() result) and current server clock time to Streaming Replication data messages. These are not currently used on the slave side but seem likely to be useful in future, and it'd be better not to change the Streaming Replication protocol after release. Per discussion. Also do some minor code review and cleanup on walsender.c, and improve the protocol documentation.
In pgsql/src/backend/replication/walsender.c, adjust misleading comment in walsender.c. We try to send all WAL data that's been written out from shared memory, but the previous phrasing might be read to say that we send only what's been fsync'd.
In pgsql/doc/src/sgml/func.sgml, improve our explanation of the OVERLAPS operator. Per gripe from Frank van Vugt.

Peter Eisentraut a commité :

Fix some inconsistent quoting of wal_level values in messages.
Translation updates for 9.0beta2.
When referring to postgresql.conf syntax, then it's without quotes (wal_level=archive); in narrative it's with double quotes. But never single quotes.
In pgsql/src/backend/libpq/hba.c, fix reference to nonexistent configure option --enable-ssl -> --with-openssl

Marc Fournier a commité :

Tag 9.0beta2.

Michael Meskes a commité :

Added variable handling for RETURNING clause to ecpg. While the values were correctly returned they were not moved into C variables as they should be. Closes: Bug #5489.

Correctifs rejetés (à ce jour)

Bruce Momjian's patches to allow setting wal_keep_segments to -1, which would mean, "never get rid of any." This was agreed not to be a good idea.
Pavel Stehule's patch to add new custom GUCs for date and time formats. Too many GUCs.

Correctifs en attente

Fujii Masao sent in three patches to fix streaming replication.
Jan Urbanski and Tom Lane traded patches to fix tsvector stats.
Peter Eisentraut sent in a patch to allow a client to authenticate a server over unix-domain sockets.
Tom Lane sent in a WIP patch to fix some some misbehavior on INSERT-only tables.
Andy Balholm sent in a WIP patch to allow dividing money by money.
Daniele Varrazzo sent in a patch to implement a regexp_match() function which returns an array rather than a SETOF matches as regexp_matches() does.
KaiGai Kohei sent two different patches intended to close some information leaks in VIEWs.
Dean Rasheed sent in a patch to fix the docs for ALTER TABLE ... DISABLE/ENABLE TRIGGER. They are out of date.

Traduction du manuel de la 9.0 beta 2

2010-06-06T22:09:00+00:00

La beta 2 de la 9.0 sort aujourd'hui (oui, on est déjà lundi, même si c'est de peu), tout comme la version 1.12 beta 2 de pgAdmin.

J'en profite pour dire que j'ai fait le merge de la traduction vers la beta 2 et que j'ai commencé sérieusement la traduction. On est passé de 247 fichiers à traduire à 32. C'est évidemment les plus gros qui restent...

Bref, pour les impatients, le manuel français de la 9.0 est disponible. Mais attention, il y a toujours des (plus ou moins gros) morceaux en anglais.

Nouvelles hebdomadaires de PostgreSQL - 31 mai 2010

2010-06-05T00:31:16+00:00

Les résultats de l'élection du bureau de PostgreSQL EU Board ont été publiés : http://blog.hagander.net/archives/169-PostgreSQL-Europe-election-results.html

[ndt: différentes migrations vers Git: en projet pour le cœur de PostgreSQL et déjà en place pour la documentation Fr]

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

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) du 11 au 13 juin. Nos PG-gourous Joshua Drake et Andrew Dunstan donneront des présentations à ne pas manquer : http://southeastlinuxfest.org/
Conférence de Michael Renner au Netways OSDC à Nuremberg (All.) les 23 & 24 juin 2010 : http://www.netways.de/osdc/y2010/programm/
CHAR(10), la conférence PostgreSQL dédiée au clustering, à la haute-disponibilité et à la réplication vient d'ouvrir les inscriptions en ligne et les réservations. 2 & 3 juillet 2010, Oriel College, Université d'Oxford (Royaume-Uni) : http://www.char10.org/
Le PDXPUG Day est programmé pour le 18 juillet 2010 à "l'Oregon Convention Center" à Portland. D'avantage d'informations : http://wiki.postgresql.org/wiki/PDXPUGDay2010
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.

(lien vers l'article original)

Correctifs appliqués

Bruce Momjian a commité :

In pgsql/contrib/pg_upgrade/option.c, split apart pg_upgrade user lookup and root check so '--help' shows proper default username.
In pgsql/doc/src/sgml/pgupgrade.sgml, update pg_upgrade docs to show options in alphabetical order, and improve 8.3 doc limitations paragraph.
In pgsql/contrib/pg_upgrade/info.c, in pg_upgrade, test for datallowconn instead of hardcoding template0.
In pgsql/contrib/pg_upgrade/option.c, re-order pg_upgrade 'help' options to be alphabetical.
In pgsql/contrib/pg_upgrade/IMPLEMENTATION.jp, add Japanese Implementation file to CVS.
In /doc/src/sgml/pgupgrade.sgml, add pg_upgrade docs about binary compatibility, per Robert Haas.
Modify pg_standby, pgbench, and pg_upgrade manual pages to be consistent in their display of command-line options with other client applications.
In pgsql/contrib/pg_upgrade/IMPLEMENTATION, update pg_upgrade IMPLEMENTATION doc file to match current 9.0 behavior.
Remove IMPLEMENTATION.jp file from pg_upgrade docs; still in pgFoundry for pg_migrator, per suggestion from Magnus Hagander.
In pgsql/doc/src/sgml/maintenance.sgml, document pgFouine and check_postgres as log analysis options.
In pgsql/doc/src/sgml/maintenance.sgml, fix SGML markup.
In pgsql/doc/src/sgml/installation.sgml, document use of VPATH builds. David Fetter.
In pgsql/src/backend/executor/execUtils.c, add C comment that we will have to remove an exclusion constraint check if we ever implement '<>' index opclasses. Jeff Davis.
In pgsql/doc/src/sgml/ref/create_domain.sgml, document that NOT NULL domain constraints are not always honored.
Clarify the meaning of "trusted language" in the documentation.

Michael Meskes a commité :

Added a configure test for "long long" datatypes. So far this is only used in ecpg and replaces the old test that was kind of hackish.
Replace self written 'long long int' configure test by standard 'AC_TYPE_LONG_LONG_INT' macro call.

Tom Lane a commité :

In pgsql/src/backend/optimizer/plan/createplan.c, fix oversight in construction of sort/unique plans for UniquePaths. If the original IN operator is cross-type, for example int8 = int4, we need to use int4 < int4 to sort the inner data and int4 = int4 to unique-ify it. We got the first part of that right, but tried to use the original IN operator for the equality checks. Per bug #5472 from Vlad Romascanu. Backpatch to 8.4, where the bug was introduced by the patch that unified SortClause and GroupClause. I was able to take out a whole lot of on-the-fly calls of get_equality_op_for_ordering_op(), but failed to realize that I needed to put one back in right here :-(
In pgsql/src/interfaces/libpq/fe-secure.c, add missing newlines to some SSL-related error messages. Noted while testing.
In pgsql/src/backend/libpq/be-secure.c, tell openssl to include the names of the root certs the server trusts in requests for client certs. This lets a client with a keystore select the appropriate client certificate to send. In particular, this is necessary to get Java clients to work in all but the most trivial configurations. Per discussion of bug #5468. Craig Ringer
In pgsql/src/backend/libpq/be-secure.c, minor editorialization for be-secure.c: fix comments and some formatting infelicities.
In pgsql/src/backend/libpq/hba.c, the message style police pay a visit to hba.c.
In pgsql/src/backend/libpq/auth.c, fix bogus error message for SSL-cert authentication, due to lack of a uaCert entry in auth_failed(). Put the switch entries into a sane order, namely the one the enum is declared in.
Rearrange libpq's SSL initialization to simplify it and make it handle some additional cases correctly. The original coding failed to load additional (chain) certificates from the client cert file, meaning that indirectly signed client certificates didn't work unless one hacked the server's root.crt file to include intermediate CAs (not the desired approach). Another problem was that everything got loaded into the shared SSL_context object, which meant that concurrent connections trying to use different sslcert settings could well fail due to conflicting over the single available slot for a keyed certificate. To fix, get rid of the use of SSL_CTX_set_client_cert_cb(), which is deprecated anyway in the OpenSSL documentation, and instead just unconditionally load the client cert and private key during connection initialization. This lets us use SSL_CTX_use_certificate_chain_file(), which does the right thing with additional certs, and is lots simpler than the previous hacking about with BIO-level access. A small disadvantage is that we have to load the primary client cert a second time with SSL_use_certificate_file, so that that one ends up in the correct slot within the connection's SSL object where it can get paired with the key. Given the other overhead of making an SSL connection, that doesn't seem worth worrying about. Per discussion ensuing from bug #5468.
Improve SSL-related documentation. Explain how to deal with certificate chains, do assorted wordsmithing.
In pgsql/src/backend/commands/indexcmds.c, make CREATE INDEX run expression preprocessing on a proposed index expression before it checks whether the expression is immutable. This covers two cases that were previously handled poorly: 1. SQL function inlining could reduce the apparent volatility of the expression, allowing an expression to be accepted where it previously would not have been. As an example, polymorphic functions must be marked with the worst-case volatility they have for any argument type, but for specific argument types they might not be so volatile, so indexing could be allowed. (Since the planner will refuse to inline functions in cases where the apparent volatility of the expression would increase, this won't break any cases that were accepted before.) 2. A nominally immutable function could have default arguments that are volatile expressions. In such a case insertion of the defaults will increase both the apparent and actual volatility of the expression, so it is *necessary* to check this before allowing the expression to be indexed. Back-patch to 8.4, where default arguments were introduced.
In pgsql/src/include/catalog/pg_proc.h, fix the volatility marking of textanycat() and anytextcat(): they were marked immutable, but that is wrong in general because the cast from the polymorphic argument to text could be stable or even volatile. Mark them volatile for safety. In the typical case where the cast isn't volatile, the planner will deduce the correct expression volatility after inlining the function, so performance is not lost. The just-committed fix in CREATE INDEX also ensures this won't break any indexing cases that ought to be allowed. Per discussion, I'm not bumping catversion for this change, as it doesn't seem critical enough to force an initdb on beta testers.
In pgsql/src/backend/utils/misc/ps_status.c, change ps_status.c to explicitly track the current logical length of ps_buffer. This saves cycles in get_ps_display() on many popular platforms, and more importantly ensures that get_ps_display() will correctly return an empty string if init_ps_display() hasn't been called yet. Per trouble report from Ray Stell, in which log_line_prefix %i produced junk early in backend startup. Back-patch to 8.0. 7.4 doesn't have %i and its version of get_ps_display() makes no pretense of avoiding pad junk anyhow.
In pgsql/src/backend/executor/nodeMergejoin.c, rejigger mergejoin logic so that a tuple with a null in the first merge column is treated like end-of-input, if nulls sort last in that column and we are not doing outer-join filling for that input. In such a case, the tuple cannot join to anything from the other input (because we assume mergejoinable operators are strict), and neither can any tuple following it in the sort order. If we're not interested in doing outer-join filling we can just pretend the tuple and its successors aren't there at all. This can save a great deal of time in situations where there are many nulls in the join column, as in a recent example from Scott Marlowe. Also, since the planner tends to not count nulls in its mergejoin scan selectivity estimates, this is an important fix to make the runtime behavior more like the estimate. I regard this as an omission in the patch I wrote years ago to teach mergejoin that tuples containing nulls aren't joinable, so I'm back-patching it. But only to 8.3 --- in older versions, we didn't have a solid notion of whether nulls sort high or low, so attempting to apply this optimization could break things.
Rewrite LIKE's %-followed-by-_ optimization so it really works (this time for sure ;-)). It now also optimizes more cases, such as %_%_. Improve comments too. Per bug #5478. In passing, also rename the TCHAR macro to GETCHAR, because pgindent is messing with the formatting of the former (apparently it now thinks TCHAR is a typedef name). Back-patch to 8.3, where the bug was introduced.
In pgsql/src/backend/utils/adt/like_match.c, fix oversight in the previous patch that made LIKE throw error for \ at the end of the pattern: the code path that handles \ just after % should throw error too. As in the previous patch, not back-patching for fear of breaking apps that worked before.
In pgsql/src/bin/psql/common.c, abort a FETCH_COUNT-controlled query if we observe any I/O error on the output stream. This typically indicates that the user quit out of $PAGER, or that we are writing to a file and ran out of disk space. In either case we shouldn't bother to continue fetching data. Stephen Frost.
In pgsql/doc/src/sgml/perform.sgml, add text to "Populating a Database" pointing out that bulk data load into a table with foreign key constraints eats memory. Per off-line discussion of bug #5480 with its reporter. Also do some minor wordsmithing elsewhere in the same section.
Change the notation for calling functions with named parameters from "val AS name" to "name := val", as per recent discussion. This patch catches everything in the original named-parameters patch, but I'm not certain that no other dependencies snuck in later (grepping the source tree for all uses of AS soon proved unworkable). In passing I note that we've dropped the ball at least once on keeping ecpg's lexer (as opposed to parser) in sync with the backend. It would be a good idea to go through all of pgc.l and see if it's in sync now. I didn't attempt that at the moment.
In pgsql/src/backend/tsearch/ts_typanalyze.c, fix misuse of Lossy Counting (LC) algorithm in compute_tsvector_stats(). We must filter out hashtable entries with frequencies less than those specified by the algorithm, else we risk emitting junk entries whose actual frequency is much less than other lexemes that did not get tabulated. This is bad enough by itself, but even worse is that tsquerysel() believes that the minimum frequency seen in pg_statistic is a hard upper bound for lexemes not included, and was thus underestimating the frequency of non-MCEs. Also, set the threshold frequency to something with a little bit of theory behind it, to wit assume that the input distribution is approximately Zipfian. This might need adjustment in future, but some preliminary experiments suggest that it's not too unreasonable. Back-patch to 8.4, where this code was introduced. Jan Urbanski, with some editorialization by Tom Lane.

Robert Haas a commité :

In pgsql/src/backend/postmaster/postmaster.c, more fixes for shutdown during recovery. 1. If we receive a fast shutdown request while in the PM_STARTUP state, process it just as we would in PM_RECOVERY, PM_HOT_STANDBY, or PM_RUN. Without this change, an early fast shutdown followed by Hot Standby causes the database to get stuck in a state where a shutdown is pending (so no new connections are allowed) but the shutdown request is never processed unless we end Hot Standby and enter normal running. 2. Avoid removing the backup label file when a smart or fast shutdown occurs during recovery. It makes sense to do this once we've reached normal running, since we must be taking a backup which now won't be valid. But during recovery we must be recovering from a previously taken backup, and any backup label file is needed to restart recovery from the right place. Fujii Masao and Robert Haas
In pgsql/src/bin/psql/help.c, fix psql help: \da+ is same as \da, but \daS is not. Noted by Stephen Frost.
In pgsql/src/backend/postmaster/postmaster.c, avoid starting walreceiver in states where it shouldn't be running. In particular, it's bad to start walreceiver when in state PM_WAIT_BACKENDS, because we have no provision to kill walreceiver when in that state. Fujii Masao.

Simon Riggs a commité :

Hot Standby Defer buffer pin deadlock check until deadlock_timeout has expired. During Hot Standby we need to check for buffer pin deadlocks when the Startup process begins to wait, in case it never wakes up again. We previously made the deadlock check immediately on the basis it was cheap, though clearer thinking and prima facie evidence shows that was too simple. Refactor existing code to make it easy to add in deferral of deadlock check until deadlock_timeout allowing a good reduction in deadlock checks since far few buffer pins are held for that duration. It's worth doing anyway, though major goal is to prevent further reports of context switching with high numbers of users on occasional tests.

Heikki Linnakangas a commité :

In pgsql/src/backend/replication/walsender.c, in walsender, don't sleep if there's outstanding WAL waiting to be sent, otherwise we effectively rate-limit the streaming as pointed out by Simon Riggs. Also, send the WAL in smaller chunks, to respond to signals more promptly.
In pgsql/src/backend/replication/walsender.c, thinko in previous commit: ensure that MAX_SEND_SIZE is always greater than XLOG_BLCKSZ, by defining it as 16 * XLOG_BLCKSZ rather than directly as 128k bytes.
In pgsql/src/backend/access/transam/xlog.c, adjust comment to reflect that we now have Hot Standby. Pointed out by Robert Haas.
In pgsql/doc/src/sgml/ref/savepoint.sgml, make it more clear that you need to release savepoint with RELEASE SAVEPOINT to make an older savepoint with the same name accessible. It's also possible to implicitly release the savepoint by rolling back to an earlier savepoint, but mentioning that too would make the note just more verbose and confusing. Florian Pflug.
In pgsql/doc/src/sgml/high-availability.sgml, update High Availability docs. Clarify terms master/primary standby/slave, move two paragraphs that apply to log shipping in general from the "Alternative method for log shipping" section to the earlier sections. Add varname tags where missing. Some small wording changes.
In pgsql/doc/src/sgml/high-availability.sgml, fix typos in recent doc patch. Fujii Masao.

ITAGAKI Takahiro a commité :

Mark PG_MODULE_MAGIC and PG_FUNCTION_INFO_V1 with PGDLLEXPORT independently from BUILDING_DLL. It is always __declspec(dllexport).
In pgsql/src/include/port/cygwin.h and pgsql/src/include/port/win32.h PGDLLEXPORT is __declspec (dllexport) only on MSVC, but is __declspec (dllimport) on other compilers because cygwin and mingw don't like dllexport.

Peter Eisentraut a commité :

In pgsql/doc/src/sgml/syntax.sgml, small correction/clarification in discussion of Unicode literals.

Correctifs rejetés (à ce jour)

Stephen Frost's in a patch to move a "long long" check to c.h. The actual problem, if it needs fixing, needs to be fixed in autoconf.

Correctifs en attente

KaiGai Kohei sent in six revisions of a patch to rework Robert Haas's patch to add an ExecutorCheckPerms() hook.
Fujii Masao sent in two more revisions of the patch to fix smart shutdown during recovery.
Craig Ringer sent in two revisions of a patch to fix an issue with SSL certificates.
Simon Riggs sent in a patch to fix the sporadically reduced speed and context switch storm issues in Hot Standby.
Mike Fowler sent in three revisions of a patch to add XMLEXISTS from the SQL/XML section of the SQL standard.
Jonathan Leto and Josh Tolley traded patches to document the PL template handler better.
Stephen Frost sent in a patch to do regression tests on psql's backslash commands.
ITAGAKI Takahiro sent in a patch to fix an issue where fillfactor in TOAST tables is set to 0, which is not always right.
Robert Haas sent in a patch to add a get_whatever_oid() function. This factors out much code duplication.
Simon Riggs sent in another revision of the patch to fix keepalive issues in max_standby_delay.
Peter Eisentraut sent in a patch for 9.1 that adds functions pg_stat_get_backend_client_addr and pg_stat_get_backend_client_port.

Et hop, un dépôt git pour la traduction des manuels de PostgreSQL et de Slony

2010-06-02T17:04:00+00:00

Marc Cousin a beaucoup bossé là-dessus, et il a surtout bien bossé. Le résultat est disponible sur github.com. Le dépôt SVN devient donc inutile et sera archivé rapidement. Pour récupérer le dépôt, c'est très simple. Il vous suffit d'utiliser cette commande :

 git clone git://github.com/gleu/pgdocs_fr.git

et quelques secondes après, vous disposez de toutes les branches, de tous les tags... bref, du dépôt complet des fichiers XML. Cool, non ?

Merci Marc, j'attendais ça depuis un bon moment. Maintenant, tout se fait sur le dépôt git. Si vous voulez les droits d'écriture dessus, il me semble qu'il faut absolument un compte sur github (ouverture gratuite et rapide) et me donner le nom du compte. Allez, je retourne au boulot.

La traduction de la 9.0 peut commencer

2010-05-30T17:59:00+00:00

Le merge est terminé depuis un bon moment. J'attendais de pouvoir proposer une interface simpliste pour la réservation des fichiers et surtout la récupération du diff entre ancienne version et nouvelle version de chaque fichier.

Cet après-midi, j'ai donc écrit cette interface, ainsi qu'un outil pour intégrer toutes ces informations dans une base de données. Le résultat est disponible à cette URL : http://www.postgresql.fr/~guillaume/traduction/liste.php

Alors, oui, c'est en grosse partie moche, sauf la partie visualisation du patch. Ça n'a pas beaucoup de fonctionnalités. Remarquez que c'est clairement pas le but. Je me fous de la présentation en dehors du patch. Mon but est de fournir une interface simple permettant de travailler pour se mettre au travail le plus vite possible. C'est chose faite. Je suis content

Pour réserver un fichier, il suffit de cliquer sur le nom du fichier, puis d'indiquer son nom dans le champ texte « Traducteur ». Le patch se trouve en dessous. Si vous ne disposez pas d'un accès au SVN, je peux vous fournir le fichier. Il suffit de m'envoyer un mail à guillaume at lelarge point info. Une fois le fichier traduit, il suffit là-aussi de me l'envoyer. Je l'intègrerais dans le SVN en vous mettant comme traducteur.

Merci.

Nouvelles hebdomadaires de PostgreSQL - 16 mai 2010

2010-05-29T15:04:51+00:00

Les mises à jour correctrices [ndt: et de sécurité] 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25 et 7.4.29 seront disponibles sous peu. Préparez-vous !

Les élections du bureau de PostgreSQL EU courent jusqu'au 23 mai 2010 : https://www.postgresql.eu/elections/

Conférence de Michael Renner au Netways OSDC à Nuremberg (All.) les 23 & 24 juin 2010 : http://www.netways.de/osdc/y2010/programm/

Le PDXPUG Day est programmé pour le 18 juillet 2010 à "l'Oregon Convention Center" à Portland. D'avantage d'informations : http://wiki.postgresql.org/wiki/PDXPUGDay2010

Les nouveautés des produits dérivés

tail_n_mail 1.10.3, un programme Perl pour scanner les fichiers de logs et envoyer les résultats par mail : http://bucardo.org/wiki/Tail_n_mail
neo_my2pg 0.8, un utilitaire de conversion depuis MySQL : http://pgfoundry.org/projects/my2postgres/
pgAdmin 1.10.3, une interface graphique de gestion pour PostgreSQL : http://www.pgadmin.org/download/
pgbouncer 1.3.3, un gestionnaire léger de connexions pour PostgreSQL : http://pgfoundry.org/projects/pgbouncer/
pglesslog 1.4.1, un ensemble d'outils visant à réduire la taille des WALs : http://pglesslog.projects.postgresql.org/
psycopg2 2.2.0, un connecteur Python pour PostgreSQL : http://initd.org/psycopg/

La fonctionnalité 9.0 de la semaine

pg_ctl a maintenant une option "initdb".

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
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/
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) du 11 au 13 juin. Nos PG-gourous Joshua Drake et Andrew Dunstan donneront des présentations à ne pas manquer : 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 et Devrim Gunduz. Traduction par l'équipe PostgreSQLFr sous licence CC BY-NC-SA.

(lien vers l'article original)

Correctifs appliqués

Tom Lane a commité :

In pgsql/src/backend/optimizer/plan/planagg.c, when adding a "target IS NOT NULL" indexqual to the plan for an index-optimized MIN or MAX, we must take care to insert the added qual in a legal place among the existing indexquals, if any. The btree index AM requires the quals to appear in index-column order. We didn't have to worry about this before because "target IS NOT NULL" was just treated as a plain scan filter condition; but as of 9.0 it can be an index qual and then it has to follow the rule. Per report from Ian Barwick.
In pgsql/src/backend/optimizer/prep/prepunion.c, fix incorrect patch that removed permission checks on inheritance child tables --- the parent table no longer got checked, either. Per bug #5458 from Takahiro Itagaki.
In pgsql/src/backend/postmaster/pgarch.c, cause the archiver process to adopt new postgresql.conf settings (particularly archive_command) as soon as possible, namely just before issuing a new call of archive_command, even when there is a backlog of files to be archived. The original coding would only absorb new settings after clearing the backlog and returning to the outer loop. Per discussion. Back-patch to 8.3. The logic in prior versions is a bit different and it doesn't seem worth taking any risks of breaking it.
Add PKST to the default set of timezone abbreviations. Per discussion, if we have PKT in there then PKST should be too. Also, fix mistaken claim that these abbrevs are not known to zic.
Update time zone data files to tzdata release 2010j: DST law changes in Argentina, Australian Antarctic, Bangladesh, Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia. Historical corrections for Taiwan.
Clean up unnecessary unportability and compiler warnings by removing the cmp parameter for pg_scandir(). The code failed to support this anyway for Sun/Windows, so pretending we could accept a parameter other than NULL was just asking for trouble.
Hook pg_upgrade into the contrib makefile structure so it gets built on the buildfarm.
Preliminary release notes for releases 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, 7.4.29.
In pgsql/contrib/pg_upgrade_support/Makefile, fix wrong subdir. Per buildfarm.
Use "TOAST table" in place of the vague, not-used-elsewhere phrase "supplementary storage table".
In pgsql/doc/src/sgml/rules.sgml, use an entity instead of non-ASCII letter. Thom Brown.
Fix up lame idea of not using autoconf to determine if platform has scandir(). Should fix buildfarm failures.
In pgsql/contrib/pg_upgrade/file.c, spell __darwin__ correctly, to suppress compiler warning on OSX.
In pg_upgrade, get rid of unsafe sprintf and snprintf usages. Per compiler warnings.
In pgsql/contrib/pg_upgrade/controldata.c, remove another unsafe use of random data as a format string.
In pgsql/contrib/pg_upgrade/info.c, fix another obvious bug pointed out by a compiler warning.
In pgsql/src/include/port.h, spell __NetBSD__ the same way everywhere. Per Giles Lean.
In pgsql/doc/src/sgml/ref/pg_restore.sgml, improve documentation of pg_restore's -l and -L switches to point out their interactions with filtering switches, such as -n and -t. Per a complaint from Russell Smith.
Ensure that pg_restore -l will output DATABASE entries whether or not -C is specified. Per bug report from Russell Smith and ensuing discussion. Since this is a corner case behavioral change, I'm going to be conservative and not back-patch it. In passing, also rename the RestoreOptions field for the -C switch to something less generic than "create".

ITAGAKI Takahiro a commité :

In pgsql/src/backend/catalog/pg_proc.c, set per-function GUC settings during validating the function. Now validators work properly even when the settings contain parameters that affect behavior of the function, like search_path. Reported by Erwin Brandstetter.
In pgsql/src/backend/po/ja.po, remove CRs.

Robert Haas a commité :

In pgsql/doc/src/sgml/ref/cluster.sgml, mention related ALTER TABLE variants in documentation for CLUSTER. As suggested by Andy Lester.
In pgsql/src/include/utils/rbtree.h, change typedef for rb_appendator to avoid conflict with C++ reserved words. Fixes a complaint from src/tools/pginclude/cpluspluscheck reported by Peter Eisentraut.
In pgsql/src/backend/postmaster/postmaster.c, we now accept read-only connections in state PM_RECOVERY_CONSISTENT.
Rename PM_RECOVERY_CONSISTENT and PMSIGNAL_RECOVERY_CONSISTENT. The new names PM_HOT_STANDBY and PMSIGNAL_BEGIN_HOT_STANDBY more accurately reflect their actual function.
In pgsql/doc/src/sgml/xfunc.sgml, fix longstanding typo in V1 calling conventions documentation. Erik Rijkers
In pgsql/doc/src/sgml/xfunc.sgml, insert line breaks in two places in SQL functions documentation. This avoids a formatting problem in the PDF output. In the HTML output this isn't necessary, but we've done similar things elsewhere in the documentation so I think it's OK to do it here, too. I've refrained from breaking a longish error message which also causes problems for the PDF output, because that would make the HTML output look wrong. Erik Rijkers.

Bruce Momjian a commité :

Add pg_upgrade to /contrib; will be in 9.0 beta2. Add documentation. Supports migration from PG 8.3 and 8.4.
Add pgsql/contrib/pg_upgrade/TODO file to CVS.
Add pgsql/contrib/pg_upgrade/IMPLEMENTATION file to CVS.
In pgsql/contrib/pg_upgrade/info.c, small formatting adjustment.
Add PGFILEDESC description to Makefiles for all /contrib executables. Add PGAPPICON to all executable makefiles.
Move pg_upgrade TODO to TODO wiki.
In pgsql/src/backend/Makefile, remove Makefile PGFILEDESC tag that the postmaster is an executable.
In pgsql/src/backend/Makefile, update comment about why postmaster doesn't get an icon.
Move pg_upgrade shared library out into its own /contrib directory (pg_upgrade_support).
In pgsql/doc/src/sgml/release-9.0.sgml, update release notes to current.
In pgsql/doc/src/sgml/release-9.0.sgml, fix HISTORY.html build using , not </>.
In pgsql/doc/src/sgml/pgupgrade.sgml, comment out EnterpriseDB Advanced Server mention in SGML docs.
Remove all mentions of EnterpriseDB Advanced Server from pg_upgrade; EDB must maintain their own patch set for this.
Use NAMEDATALEN instead of local define. Modify path separators for Win32. Per ideas from Takahiro Itagaki.
In pgsql/contrib/pg_upgrade/file.c, change bsdi define to __bsdi__.
Use __bsdi__ consistently.
In pgsql/contrib/pg_upgrade/file.c, adjust pg_upgrade BSD defines for scandir(), per report from Giles Lean.

Peter Eisentraut a commité :

Update config.guess and config.sub.
Translation update
Fix vpath installation from distribution tarball (bug #5447)
In pgsql/src/nls-global.mk, avoid error from mkdir if no languages are to be installed mkinstalldirs used to handle no arguments, but mkdir doesn't. Also remove the .SILENT setting, that was previously removed from Makefile.global as well.
Translation update

Simon Riggs a commité :

In pgsql/src/backend/tcop/postgres.c, give most recovery conflict errors a retryable error code. From recent requests and discussions with Yeb Havinga and Kevin Grittner.
Cleanup initialization of Hot Standby. Clarify working with reanalysis of requirements and documentation on LogStandbySnapshot(). Fixes two minor bugs reported by Tom Lane that would lead to an incorrect snapshot after transaction wraparound. Also fix two other problems discovered that would give incorrect snapshots in certain cases. ProcArrayApplyRecoveryInfo() substantially rewritten. Some minor refactoring of xact_redo_apply() and ExpireTreeKnownAssignedTransactionIds().
In pgsql/src/backend/access/transam/xact.c, ensure that top level aborts call XLogSetAsyncCommit(). Not doing so simply leads to data waiting in wal_buffers which then causes later commits to potentially do emergency writes and for all forms of replication to be potentially delayed without need or benefit. Issue pointed out exactly by Fujii Masao, following bug report by Robert Haas on a separate though related topic.
Add many new Asserts in code and fix simple bug that slipped through without them, related to previous commit. Report by Bruce Momjian.
In pgsql/src/backend/access/transam/xlog.c, fix bug in processing of checkpoint time for max_standby_delay. Latest log time was incorrectly set, typically leading to dates in the past, which would cause more cancellations in Hot Standby on a quiet server.

Andrew Dunstan a commité :

In pgsql/src/tools/msvc/Mkvcbuild.pm, add missing library and include support for pg_upgrade to MSVC build system.

Magnus Hagander a commité :

Fix some spelling errors. Thom Brown.
In pgsql/src/tools/msvc/Mkvcbuild.pm, properly support multi-line entires (such as OBJS=) when building PROGRAM, not just MODULE, in contrib.
Assorted fixes to make pg_upgrade build on MSVC. 1. There is no chmod() on Windows. 2. Must always use the 3-parameter version of open(). 3. There is no dynloader.h - but it also appears unnecessary on all platforms. 4. Don't include shlobj.h because it causes compile errors, and from what I can see it's not actually used. This may need to be added back for mingw and/or cygwin in the worst case.

Marc Fournier a commité :

Tag 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, 7.4.29.

Heikki Linnakangas a commité :

In pgsql/contrib/pg_standby/pg_standby.c, fix typos in comments, spotted by Josh Kupershmidt.

Correctifs rejetés (à ce jour)

Greg Sabino Mullane's patch to change pg_dump not to use CREATE OR REPLACE LANGUAGE when talking to pre-9.0 databases. There never was a guarantee that the output of pg_dump would be backward-compatible.

Correctifs en attente

ITAGAKI Takahiro sent in a patch to change the search_path check for function bodies to the current search_path, where they had been using the one at create time.
Mike Fowler sent in a patch to add a function xpath_exists() for 9.1.
Alexander Korotkov sent in two revisions of a patch to make the levenshtein distance function in contrib/fuzzystrmatch work with multibyte character sets in 9.1.
Simon Riggs sent in a patch to change the startup code for Hot Standby.
Stephen Frost sent in a patch to add a handler for SIGCHLD to psql. This is for 9.1.
Simon Riggs sent in a patch to add a keepalive message to ensure max_standby_delay is useful. Heikki Linnakangas responded with one which rearranges the walsender loops slightly so that XLogSend() now only sends up to MAX_SEND_SIZE bytes (== XLOG_SEG_SIZE / 2) in one round and returns to the main loop after that even if there's unsent WAL, and the main loop no longer sleeps if there's unsent WAL. Simon Riggs sent in another with wait processing cleanup.
Joachim Wieland sent in a patch to fix some locking behavior for 9.1 in the case of SERIALIZABLE transactions.
Robert Haas sent in a patch to implement a fix for smart shutdown in recovery.

Nouvelles hebdomadaires de PostgreSQL - 23 mai 2010

2010-05-29T15:04:26+00:00

Nouvelles hebdomadaires de PostgreSQL - 23 mai 2010

CHAR(10), la conférence PostgreSQL dédiée au clustering, à la haute-disponibilité et à la réplication vient d'ouvrir les inscriptions en ligne et les réservations. 2 & 3 juillet 2010, Oriel College, Université d'Oxford (Royaume-Uni) : http://www.char10.org/

Les nouveautés des produits dérivés

Cybercluster 2.0 : http://www.cybertec.at/en/cybercluster-2-0-synchronous-postgresql-replication
Muldi-D 0.129.1, une spécification de langage objet-relationnel destiné, entre autres systèmes, à PostgreSQL : http://archives.postgresql.org/pgsql-announce/2010-05/msg00020.php
MyJSQLView 3.17, un utilitaire graphique utilisable avec PostgreSQL : http://dandymadeproductions.com/projects/MyJSQLView/index.html
PostgreDAC 2.5.5, un "builder" Delphi/C++ pour PostgreSQL : http://microolap.com/products/connectivity/postgresdac/download/
psycopg2 2.2.1, un connecteur Python pour PostgreSQL : http://initd.org/psycopg/
Devrim GUNDUZ a publié les RPMs pour les mises à jour de sécurité 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25 et 7.4.29 : http://yum.pgrpms.org
2ndQuadrant vient d'ouvrir une succursale française : http://www.2ndQuadrant.fr/
Les mises à jour de sécurité 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25 et 7.4.29 sont disponibles. Mettez à jour dès que possible : http://www.postgresql.org/docs/current/static/release.html
Les sommes de contrôle des fichiers Tar sont disponibles à cette adresse : http://www.gtsm.com/postgres_sigs.html
Postgres-XC 0.9.1 : http://postgres-xc.sourceforge.net/

La fonctionnalité 9.0 de la semaine

Les Large Objects (LO ou BLOB) bénéficient maintenant de contrôles d'accès comme les autres objets en base de donnée.

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

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) du 11 au 13 juin. Nos PG-gourous Joshua Drake et Andrew Dunstan donneront des présentations à ne pas manquer : http://southeastlinuxfest.org/
Conférence de Michael Renner au Netways OSDC à Nuremberg (All.) les 23 & 24 juin 2010 : http://www.netways.de/osdc/y2010/programm/
Le PDXPUG Day est programmé pour le 18 juillet 2010 à "l'Oregon Convention Center" à Portland. D'avantage d'informations : http://wiki.postgresql.org/wiki/PDXPUGDay2010
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 et Devrim Gunduz. Traduction par l'équipe PostgreSQLFr sous licence CC BY-NC-SA.

(lien vers l'article original)

Correctifs appliqués

Andrew Dunstan a commité :

Abandon the use of Perl's Safe.pm to enforce restrictions in plperl, as it is fundamentally insecure. Instead apply an opmask to the whole interpreter that imposes restrictions on unsafe operations. These restrictions are much harder to subvert than is Safe.pm, since there is no container to be broken out of. Backported to release 7.4. In releases 7.4, 8.0 and 8.1 this also includes the necessary backporting of the two interpreters model for plperl and plperlu adopted in release 8.2. In versions 8.0 and up, the use of Perl's POSIX module to undo its locale mangling on Windows has become insecure with these changes, so it is replaced by our own routine, which is also faster. Nice side effects of the changes include that it is now possible to use perl's "strict" pragma in a natural way in plperl, and that perl's $a and $b variables now work as expected in sort routines, and that function compilation is significantly faster. Tim Bunce and Andrew Dunstan, with reviews from Alex Hunsaker and Alexey Klyukin. Security: CVE-2010-1169
In pgsql/src/tools/msvc/Mkvcbuild.pm, fix MSVC builds for recent plperl changes. Go back to version 8.2, which is where we started supporting MSVC builds. Security: CVE-2010-1169.
In pgsql/src/pl/plperl/plperl.c, follow up a visit from the style police.
In pgsql/src/pl/plperl/expected/plperl_init.out, fix regression tests to match error message change.

Tom Lane a commité :

Prevent PL/Tcl from loading the "unknown" module from pltcl_modules unless that is a regular table or view owned by a superuser. This prevents a trojan horse attack whereby any unprivileged SQL user could create such a table and insert code into it that would then get executed in other users' sessions whenever they call pltcl functions. Worse yet, because the code was automatically loaded into both the "normal" and "safe" interpreters at first use, the attacker could execute unrestricted Tcl code in the "normal" interpreter without there being any pltclu functions anywhere, or indeed anyone else using pltcl at all: installing pltcl is sufficient to open the hole. Change the initialization logic so that the "unknown" code is only loaded into an interpreter when the interpreter is first really used. (That doesn't add any additional security in this particular context, but it seems a prudent change, and anyway the former behavior violated the principle of least astonishment.) Security: CVE-2010-1170
Update release notes with security issues. Security: CVE-2010-1169, CVE-2010-1170
In pgsql/doc/src/sgml/config.sgml, fix index entry for lo_compat_privileges, per bug #5467 from KOIZUMI Satoru.
Fix oversight in join removal patch: we have to delete the removed relation from SpecialJoinInfo relid sets as well. Per example from Vaclav Novotny.
In pgsql/contrib/pg_upgrade/check.c, issue_warnings() has no business freeing its parameter, especially not when its sole caller does that too. Jan Matousek, via Pavel Stehule

Alvaro Herrera a commité :

In pgsql/doc/src/sgml/ref/show.sgml, make table in example less wide.

Robert Haas a commité :

In pgsql/doc/src/sgml/ref/notify.sgml, move pg_notify() details to a subsection within the NOTIFY reference page. This allows the index to reference the pg_notify() subsection specifically, rather than Notes section of the NOTIFY reference page more generally. Fujii Masao
In pgsql/src/bin/psql/command.c, unbreak \h; can't do strlen(NULL). This was broken by the following commmit. Although the original commit was backpatched all the way to 7.4, this particular bug exists only in the version applied to HEAD. http://archives.postgresql.org/pgsql-committers/2010-05/msg00058.php

Bruce Momjian a commité :

In pgsql/contrib/pg_upgrade/TESTING, add pg_upgrade TESTING files explaining a testing method.
In pgsql/contrib/pg_upgrade/pg_upgrade.c, use a 'datallowconn' check for avoiding 'template0', rather than hardcoding a 'template0' check, per suggestion from Alvaro. This might fix a problem where someone has allowed 'template0' connections, but it is a cleaner approach even if doesn't fix the bug.
In pgsql/contrib/pg_upgrade/pg_upgrade.c, for pg_upgrade, update template0's datfrozenxid and its relfrozenxids to match the behavior of autovacuum, which does this as the xid advances even if autovacuum is turned off.
In pgsql/contrib/pg_upgrade/info.c, simplify pg_upgrade queries by using IN instead of multiple OR clauses comparing the same column to multiple values.
Add command-line documentation for pg_upgrade.
In pgsql/doc/src/sgml/oid2name.sgml, restore oid2name doc change.
In pgsql/doc/src/sgml/pgupgrade.sgml, pg_upgrade doc cleanup. Stefan Kaltenbrunner
In pgsql/doc/src/sgml/pgupgrade.sgml, doc change: Rename of directory no longer required for pg_migrator 9.0. Alvaro Herrera
In pgsql/doc/src/sgml/pgupgrade.sgml, SGML markup cleanup for pg_upgrade.
In pgsql/doc/src/sgml/oid2name.sgml, show oid2name command-line arguments in documentation like we do for non-contrib command-line tools (no longer in a single table display).

Magnus Hagander a commité :

In pgsql/doc/src/sgml/pgupgrade.sgml, make pg_upgrade documentation refer to 9.0 instead of 8.4. Fujii Masao.
In pgsql/doc/src/sgml/config.sgml, refer to pg_ident.conf as config file for username mapping, as it's now used for other things than just ident authentication. Noted by Stephen Frost
In pgsql/src/timezone/pgtz.c, change the "N. Central Asia Standard Time" timezone to map to Asia/Novosibirsk on Windows. Microsoft changed the behaviour of this zone in the timezone update from KB976098. The zones differ in handling of DST, and the old zone was just removed. Noted by Dmitry Funk.

Michael Meskes a commité :

Ecpg now accepts "long long" datatypes even if "long" is 64bit wide. This used to cover the equally long "long long" type. This patch closes bug #5464.

Correctifs rejetés (à ce jour)

Pas de déception cette semaine :-)

Correctifs en attente

Stephen Frost sent in two more revisions of a patch to fix psql's ability to clean up when quitting the pager, which resulted in queries continuing to run after the pager exited.
Fujii Masao sent in two revisions of a patch to fix smart shutdown for Hot Standby.
Fujii Masao sent in a patch to distinguish normal shutdown from unexpected exit, while the server is in recovery.
Tom Lane sent in a patch to fix a performance issue with textanycat/anytextcat.
Alvaro Herrera sent in a patch to fix an issue with fillfactor on TOAST tables.
Florian Pflug sent in two revisions of a patch to fix SERIALIZABLE transactions.
Kevin Grittner sent in a WIP patch for 9.1 to do true SERIALIZABLE using predicate locking.
Joel Jacobson sent in another revision of the patch to implement pg_stat_transaction.
Robert Haas sent in a patch to add a hook called ExecutorCheckPerms(), per discussion.
Andres Freund sent in a patch which replaces the current CRC32 with a more efficient version from zlib.
Jeff Davis sent in a patch to change a sanity check in exclusion constraints.
Jeff Davis sent in a patch for 9.1 to add btree_gist support for the "><" operator.

Peu de temps, donc quelques news rapides

2010-05-25T17:07:00+00:00

Les nouveautés se succèdent rapidement ces temps-ci et le temps manque encore plus que d'habitude pour parler de tout de façon détaillé.

Vous avez tous dû entendre parler du pgcon qui a eu la semaine dernière à Ottawa. Il y a eu beaucoup de billets de blogs sur le déroulement des festivités. L'un des points les plus intéressants actuellement est ce qui est sorti du Developer Meeting. Le rapport donne beaucoup d'informations sur les prochains développements, que ce soit pour la 9.0 (qui, on l'a appris, devrait bien sortir cet été) et pour la 9.1. Si tout est développé pour cette version, elle promet d'être aussi intéressante que la version 9.1. Je ne peux guère parler des conférences, n'y étant pas. Les quelques échos que j'ai eu étaient très positifs. J'espère pouvoir regarder quelques vidéos sous peu.

Le fait que la 9.0 devrait bientôt sortir est une excellente nouvelle. J'avais un peu peur qu'elle soit repoussée à la rentrée. Le problème que cela pose, c'est pour la traduction de la documentation. En apprenant cela vendredi dernier, j'ai créé la branche 8.4 pour pouvoir commencer le travail. Le merge est pratiquement terminé sur mon portable, après une quinzaine d'heures de travail (oui, c'est long et chiant). Reste encore quatre fichiers, évidemment les plus gros. Je pense nénamoins que ce sera terminé en fin de semaine. Restera la traduction, mais c'est moins effrayant que la période de merge. À noter que Marc travaille sur le passage du dépôt à git, ce serait un très gros plus.

Que dire de plus. J'ai appris ce matin que j'étais élu au comité directeur de PostgreSQL Europe, ce qui est très plaisant. Mon poste sera celui de vice-trésorier, bien que cela ne semble pas très fixé.

Enfin, j'ai un nouveau portable. Le passage de l'ancien au nouveau prend pas mal de temps mais devrait être bien plus agréable (ne serait-ce que la définition de l'écran, 1440x900, c'est autre chose que l'ancien 1280x800). Bref, j'en parlerais plus une autre fois mais je vais retourner au merge.

Indexation sur une sous-chaîne de caractères dans PostgreSQL

2010-05-20T00:00:00+00:00

Tous les SGBD disposent de mécanismes d'indexation pour accélerer l'accès aux données (commande SQL "CREATE INDEX (http://www.postgresql.org/docs/current/interactive/indexes-intro.html)" pour créer un tel index). Si on connait la chaîne de caractères exacte, on la trouve dans l'index et on a tout de suite ses données. Mais si on ne connait qu'une partie de la chaîne ?

Traduction d'un peu de tout

2010-05-17T21:35:00+00:00

Le week-end dernier, j'ai travaillé sur les traductions des prochaines mises à jour. Du coup, le site français de la documentation sur PostgreSQL dispose déjà des manuels des version 8.4.4, 8.3.11, etc. J'en ai profité aussi pour mettre à jour les manuels de Slony, branche 1.2 et 2.0. Par contre, je ne sais pas quand Damien aura le temps de les mettre sur le site, surtout que ce dernier commence à dater un peu.

Dernière nouveauté de traduction, l'installeur d'EnterpriseDB est disponible en français. J'avais fait la traduction il y a un bon moment, mais les petits gars de Dave Page ont mis beaucoup de temps pour l'intégrer... jusqu'à ce que je m'aperçoive en version 9.0 beta 1 que je m'étais trompé dans l'encodage. C'est enfin corrigé et l'installeur de la 8.4.4 dispose donc de la traduction. Allez, hop, deux copies d'écran pour la peine :

Lancement de l'installeur

Installation en cours

Sympa, non ? moi, j'aime bien.

Que dire de plus... la beta 2 n'est toujours pas sortie, et ne risque pas de sortir avant au moins une semaine pour cause de PGCon, ce qui m'agace bien (qu'elle ne soit pas déjà sortie et que je ne sois pas au PGCon... sigh...). Ça sent un bon retard pour la traduction du manuel de la version 9.

Le bon côté, c'est que ça me permet de travailler sur des outils comme pgpool, pgbouncer, slony. Pour les deux premiers, j'ai proposé un patch pour ajouter les options longues. Patch accepté pour pgpool, patch que j'ai donc commité dimanche après-midi. Pas de nouvelles des développeurs de pgbouncer, peut-être en voyage pour PGCon (chanceux...). Au départ, je voulais ajouter la gestion du paramètre application_name, disponible à partir de la 9.0. Je me suis un peu cassé les dents avec les poolers de connexion. Par contre, pour Slony, ça semble bien plus simple. Je pense que je vais proposer un patch assez rapidement pour ce dernier. Il serait aussi intéressant que les pilotes le prennent en compte (je pense notamment au pilote Perl et au pilote PHP). Bref, du boulot sur la planche, ce qui est cool

pgsnap, version 0.6

2010-05-13T17:18:00+00:00

Ne voulant pas réitérer la bévue pour la version 8.4 de PostgreSQL, je me suis attelé assez rapidement à mettre à jour pgsnap pour PostgreSQL 9.0.

Ce n'est évidemment pas la seule nouveauté de cette version :

Support complet de la 9.0
- connexion utilisant le paramètre application_name
- nouveau rapport sur les ACL par défaut
- nouveau rapport sur la configuration par paire base/utilisateur;
- support des tables typées, des contraintes d'exclusion, de la configuration des tablespaces, des informations sur le Hot Standby et le Streaming Replication
Meilleur support de la 8.4
- gestion de la colonne relistemp de pg_class
- gestion des nouvelles colonnes de pg_settings
- ajout de l'heure de lancement de PostgreSQL et du dernier chargement de la configuration
Meilleur support des autres versions
- nouveau rapport sur les séquences
- nouveau rapport sur les Large Objects
- détection des modules contrib
- ajout des commentaires sur les objets.

Pour télécharger, c'est ici. Vous pouvez consulter aussi cet exemple de rapport.

J'aurais pu attendre un peu avant de sortir cette version. Cependant, je vais être maintenant bien occupé par la mise à jour de la traduction française du manuel de PostgreSQL (enfin, dès que la beta 2 sort, donc à priori rapidement). Je n'aurais plus trop de temps pour m'occuper de pgsnap en dehors de quelques corrections de bugs. Donc voilà pourquoi cette version sort dès maintenant.

Et puis, j'ai en tête un changement important pour pgsnap. Peut-être pour la prochaine version.

Nouvelles hebdomadaires de PostgreSQL - 9 mai 2010

2010-05-11T21:05:17+00:00

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.

(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.

Maintenant que l'annonce est faite...

2010-05-05T22:28:00+00:00

Enfin, pour PostgreSQL car pour pgAdmin, on attend toujours. J'ai finalement réussi à corriger un bug dans pgAdmin qui me donnait du mal. Et j'ai terminé le Visual Tour pour la version 1.12. Il ne manque vraiment plus que l'annonce de la beta 1 de pgAdmin

Bref, on est en période beta. Ça veut dire correction de bugs. Ça veut dire aussi que, pour les codeurs d'outils tiers, du boulot est en prévision pour s'assurer de la compatibilité de leur outil avec la prochaine version. On va espérer que les développeurs de Slony vont penser à ça (quoiqu'il semble me rappeler avoir vu passer un patch pour ça il y a peu, donc on peut être optimiste). Ceci dit, le mieux pour tout le monde, c'est de le tester soi-même. En ce qui me concerne, ça veut dire que j'ai du boulot pour pgsnap. Un patch récemment a permis d'utiliser pgsnap avec une 9.0, mais pas d'en tirer le meilleur profit.

Mais surtout, une beta 1 de PostgreSQL, pour moi, ça veut dire une traduction du manuel à mettre à jour. Pour les outils en ligne de commande livrés avec PostgreSQL, c'est déjà fait. Mais pas encore pour la documentation. Donc voilà, à partir de demain, c'est mon occupation principale.

Beta 1 coming up

2010-04-30T23:01:00+00:00

C'est ce moment de l'année où les tests sont de rigueur...

guillaume@laptop:~$ psql -V
psql (PostgreSQL) 9.0beta1
contient une gestion avancée de la ligne de commande

Il nous a fallu quand même ce soir trois heures de discussion, codage et test avec Dave pour finaliser la 1.12. Grand merci aux outils de type pidgin, Google Chat et autres du même type, c'est quand même bien plus efficace que le mail dans ce cadre.

Une annonce officielle sera faite lundi.

GSoC pgAdmin

2010-04-29T14:30:00+00:00

Je viens d'avoir la nouvelle par Luis. Sa proposition de projet GSoC pour pgAdmin a été acceptée. Et je suis son mentor, ce qui me fait bien plaisir.

Du coup, je viens de jeter un œil aux statuts des différentes propositions. Six ont été acceptées. Deux concernent pgAdmin, un concerne phpPgAdmin et les trois autres concernent PostgreSQL directement.

Le projet que je mentor-ise doit permettre la création d'un outil de modélisation graphique d'une base à partir de pgAdmin. Luis Ochoa est l'étudiant qui a proposé cette idée. Nous avons une grande confiance en lui. Il a déjà codé le constructeur graphique de requêtes (GQB, Graphical Query Builder) de l'éditeur de requêtes. Il connaît donc bien pgAdmin et la partie graphique. Il y a de fortes chances que le résultat de son travail sera inclus dans la 1.14.

À noter que le mentor du projet pour phpPgAdmin est Jehan-Guillaume de Rorthais. Bien content pour lui aussi.