<p><strong>Nouvelles hebdomadaires de PostgreSQL - 12 juillet 2009</strong></p> <p>Des places sont toujours disponibles pour le PgDay de San Jose, dimanche 19 juillet. Inscrivez-vous rapidement&nbsp;! <a target="_blank" href="http://wiki.postgresql.org/wiki/PgDaySanJose2009">http://wiki.postgresql.org/wiki/PgDaySanJose2009</a></p> <p>Un nouvel outil fait son apparition pour les Commitfests. Merci &agrave; Robert Haas, Brendan Jurd et de nombreux autres&nbsp;: <a target="_blank" href="http://commitfest.postgresql.org/">http://commitfest.postgresql.org/</a></p> <p><strong>Les nouveaut&eacute;s des produits d&eacute;riv&eacute;s</strong></p> <ul> <li>check_postgres 2.9.2, un plugin de Nagios pour surveiller PostgreSQL&nbsp;: <a target="_blank" href="http://bucardo.org/check_postgres/">http://bucardo.org/check_postgres/</a></li> <li>Le "PostgreSQL RPM Building Project" a publi&eacute; le "PostgreSQL 8.4 Live CD"&nbsp;: <a target="_blank" href="http://www.pglivecd.org">http://www.pglivecd.org</a></li> <li>pgbouncer 1.3.1, un gestionnaire de connexion &agrave; PostgreSQL&nbsp;: <a target="_blank" href="http://pgfoundry.org/projects/pgbouncer/">http://pgfoundry.org/projects/pgbouncer/</a></li> </ul> <p>(<a target="_blank" href="http://www.postgresql.org/community/weeklynews/pwn20090712">lien vers l'article original</a>)</p> <p><strong>Offres d'emplois autour de PostgreSQL en juillet</strong></p> <ul> <li><a target="_blank" href="http://archives.postgresql.org/pgsql-jobs/2009-07/threads.php">http://archives.postgresql.org/pgsql-jobs/2009-07/threads.php</a></li> </ul> <p><strong>PostgreSQL Local</strong></p> <ul> <li>Le pgDay San Jose est programm&eacute; pour le dimanche 19 juillet, juste avant l'OSCON. Inscription ci-dessous&nbsp;: <a target="_blank" href="http://postgresql.meetup.com/1/calendar/10626647">http://postgresql.meetup.com/1/calendar/10626647</a></li> <li>L'"OpenSQL Camp" aura lieu les 22 &amp; 23 ao&ucirc;t &agrave; S<sup>t</sup> Augustin (All.), pr&egrave;s de Bonn et de Cologne. La date limite pour les propositions de conf&eacute;rences est le 19 juillet 2009&nbsp;: <a target="_blank" href="http://opensqlcamp.org/Events/2009/Call_for_Participation">http://opensqlcamp.org/Events/2009/Call_for_Participation</a></li> <li>Le PUG allemand a obtenu un emplacement d&eacute;veloppeur au FrOSCon le dimanche 23 ao&ucirc;t 2009. L'appel &agrave; conf&eacute;rences est ouvert&nbsp;: <a target="_blank" href="http://andreas.scherbaum.la/blog/archives/573-Call-for-Papers-fuer-den-PostgreSQL-Devroom-auf-der-FrOSCon-2009.html">http://andreas.scherbaum.la/blog/archives/573-Call-for-Papers-fuer-den-PostgreSQL-Devroom-auf-der-FrOSCon-2009.html</a></li> <li>L'appel &agrave; conf&eacute;rences pour la "PyCon Argentina" est lanc&eacute; jusqu'&agrave; la date du 29 juin 2009, 23h59 ART [ndt: UTC-3 ?]. La conf&eacute;rence elle-m&ecirc;me aura lieu &agrave; Buenos Aires les 4 &amp; 5 septembre 2009&nbsp;: <a target="_blank" href="http://ar.pycon.org/2009/rfp/">http://ar.pycon.org/2009/rfp/</a></li> <li>Andreas (ads) Scherbaum enseignera au centre pour adultes de Magdeburg (All.) du 7 au 11 septembre 2009 sur le sujet "PostgreSQL for Corporate Use". D&eacute;tails ci-dessous&nbsp;: <a target="_blank" href="http://andreas.scherbaum.la/blog/archives/574-PostgreSQL-als-Bildungsurlaub.html">http://andreas.scherbaum.la/blog/archives/574-PostgreSQL-als-Bildungsurlaub.html</a></li> <li style="list-style: none; display: inline"> <p>Il y aura une conf&eacute;rence &agrave; Athens (Georgie, &Eacute;tats-Unis) le 19 septembre 2009. L'appel aux conf&eacute;rences est ouvert&nbsp;: <a target="_blank" href="http://www.postgresqlconference.org/2009/pgday/athens">http://www.postgresqlconference.org/2009/pgday/athens</a></p> </li> <li>Une suite de conf&eacute;rences est organis&eacute;e &agrave; Seattle (&Eacute;tat de Washington, &Eacute;tats-Unis) du 16 au 18 octobre 2009. L'appel &agrave; conf&eacute;rences est ouvert&nbsp;: <a target="_blank" href="http://www.postgresqlconference.org/2009/west">http://www.postgresqlconference.org/2009/west</a></li> <li>La "PGCon Brazil" prendra place &agrave; l'Unicamp de Campinas (&Eacute;tat de S&atilde;o Paulo) les 23 &amp; 24 octobre 2009. L'appel &agrave; conf&eacute;rences est lanc&eacute;&nbsp;: <a target="_blank" href="http://pgcon.postgresql.org.br/2009/chamadas.en.php">http://pgcon.postgresql.org.br/2009/chamadas.en.php</a></li> <li>Le PGDay.EU 2009 est programm&eacute; pour les 6 &amp; 7 novembre 2009 &agrave; Telecom ParisTech [ndt: ENST ?]&nbsp;: <a target="_blank" href="http://www.pgday.eu/">http://www.pgday.eu/</a></li> <li>Vos propositions de conf&eacute;rences sont attendues pour le 10<sup>&egrave;me</sup> anniversaire du JPUG. Le rassemblement aura lieu les 20 &amp; 21 novembre 2009 &agrave; Tokyo, Japan&nbsp;: <a target="_blank" href="http://archives.postgresql.org/pgsql-announce/2009-05/msg00018.php">http://archives.postgresql.org/pgsql-announce/2009-05/msg00018.php</a></li> </ul> <p><strong>PostgreSQL dans les m&eacute;dia</strong></p> <ul> <li>Planet PostgreSQL: <a target="_blank" href="http://planet.postgresql.org/">http://planet.postgresql.org/</a></li> <li>Planet PostgreSQLFr&nbsp;: <a target="_blank" href="http://planete.postgresql.fr/">http://planete.postgresql.fr/</a></li> </ul> <p><i>PostgreSQL Weekly News / les nouvelles hebdomadaires vous sont offertes cette semaine par David Fetter, Josh Berkus et Devrim Gunduz. Traduction par l'&eacute;quipe PostgreSQLFr sous licence CC BY-NC-SA.</i></p> <p><i>Proposez vos articles ou annonces avant dimanche 15:00 (heure du Pacifique). Merci de les envoyer en anglais &agrave; david (a) fetter.org, en allemand &agrave; pwn (a) pgug.de, en italien &agrave; pwn (a) itpug.org.</i></p> <p><strong>Correctifs appliqu&eacute;s</strong></p> <p>Peter Eisentraut a commit&eacute;&nbsp;:</p> <ul> <li>In pgsql/src/bin/psql/describe.c, show definition of index columns in \d on index. This adds a column called "Definition" to the output of psql \d on an index, which shows the full expression behind the index column. For indexes on plain columns, this is redundant, but for expression indexes, this reveals the real expression. Author: Khee Chin.</li> <li>More sensible character_octet_length. For character types with typmod, character_octet_length columns in the information schema now show the maximum character length times the maximum length of a character in the server encoding, instead of some huge value as before.</li> <li>In pgsql/src/bin/psql/describe.c, sort child tables by name instead of OID in \d+ display. This was an oversight in the recent patch. Found by Tom Lane.</li> <li>In pgsql/src/bin/psql/describe.c, psql backward compatibility fix. For servers older than 8.3, sort display of child tables by relname instead of oid::regclass::text, because the cast from regclass to text did not work back then. The older display may be slightly worse when different schemas are involved, but that should be rare enough.</li> <li>In pgsql/src/makefiles/pgxs.mk, when calling unsupported "make check" with a pgxs module, return a nonzero exit code.</li> <li>In pgsql/doc/src/sgml/acronyms.sgml, correct what ISO stands for.</li> <li>Alter some gratuitous uses of "ANSI" when "SQL standard" might have been meant or the reference to a standard was unnecessary.</li> </ul> <p>Tom Lane a commit&eacute;&nbsp;:</p> <ul> <li>Fix set_append_rel_pathlist() to deal intelligently with cases where substituting a child rel's output expressions into the appendrel's restriction clauses yields a pseudoconstant restriction. We might be able to skip scanning that child rel entirely (if we get constant FALSE), or generate a one-time filter. 8.3 more or less accidentally generated plans that weren't completely stupid in these cases, but that was only because an extra recursive level of subquery_planner() always occurred and allowed const-simplification to happen. 8.4's ability to pull up appendrel members with non-Var outputs exposes the fact that we need to work harder here. Per gripe from Sergey Burladyan.</li> <li>In pgsql/src/backend/utils/adt/timestamp.c, use floor() not rint() when reducing precision of fractional seconds in timestamp_trunc, timestamptz_trunc, and interval_trunc(). This change only affects the float-datetime case; the integer-datetime case already behaved like truncation instead of rounding. Per gripe from Mario Splivalo. This is a pre-existing issue but I'm choosing not to backpatch, because it's such a corner case and there have not been prior complaints. The issue is largely moot anyway given the trend towards integer datetimes.</li> <li>In pgsql/src/bin/psql/describe.c, code review for patch to show definition of index columns in \d on index. Safely schema-qualify the pg_get_indexdef call, make the query a bit prettier in -E mode, remove useless join to pg_index, make it more obvious that the header[] array is not overrun.</li> <li>In pgsql/src/include/catalog/pg_proc.h, fix typo in comment.</li> <li>In pgsql/src/backend/catalog/information_schema.sql, query in SQL function still not schema-safe; add a couple more pg_catalog. qualifications.</li> <li>In pgsql/src/backend/utils/mb/mbutils.c, don't use 'return' where you should use 'PG_RETURN_xxx'.</li> <li>In pgsql/src/bin/psql/describe.c, just a little more schema-qualification ...</li> <li>In pgsql/doc/src/sgml/datatype.sgml, add missing HOUR TO SECOND option to list of possible INTERVAL field sets, as noted by Sebastien Flaesch. Also update the claim that we simply throw away fields outside this set --- that got changed later to only discard less-significant fields.</li> <li>In pgsql/src/backend/postmaster/postmaster.c, remove no-longer-necessary transmission of postmaster's LC_COLLATE and LC_CTYPE settings to children via BackendParameters. Per discussion, the postmaster is now just using system defaults anyway, so we might as well save a few cycles during backend startup.</li> <li>In pgsql/contrib/xml2/xslt_proc.c, fix xslt_process() to ensure that it inserts a NULL terminator after the last pair of parameter name/value strings, even when there are MAXPARAMS of them. Aboriginal bug in contrib/xml2, noted while studying bug #4912 (though I'm not sure whether there's something else involved in that report). This might be thought a security issue, since it's a potential backend crash; but considering that untrustworthy users shouldn't be allowed to get their hands on xslt_process() anyway, it's probably not worth getting excited about.</li> <li>In pgsql/src/backend/optimizer/path/costsize.c, fix set_rel_width() to do something reasonable with non-Var items in a RelOptInfo targetlist. It used to be that the only possibility other than a Var was a RowExpr representing a whole-row child Var, but as of 8.4's expanded ability to flatten appendrel members, we can get arbitrary expressions in there. Use the expression's type info and get_typavgwidth() to produce an at-least-marginally-sane result. Note that get_typavgwidth()'s fallback estimate (32 bytes) is the same as what was here before, so there will be no behavioral change for RowExprs. Noted while looking at recent gripe about constant quals pushed down to FunctionScan appendrel members ... not only were we failing to recognize the constant qual, we were getting the width estimate wrong :-(</li> <li>Move some declarations in the raw-parser header files to create a clearer distinction between the external API (parser.h) and declarations that only need to be visible within the raw parser code (gramparse.h, which now is only included by parser.c, gram.y, scan.l, and keywords.c). This is in preparation for the upcoming change to a reentrant lexer, which will require referencing YYSTYPE in the declarations of base_yylex and filtered_base_yylex, hence gram.h will have to be included by gramparse.h. We don't want any more files than absolutely necessary to depend on gram.h, so some cleanup is called for.</li> <li>Fix up PGDLLIMPORT marking for standard_conforming_strings. Moving it into a header file that plpgsql's scan.l can see broke the previous kluge. Per buildfarm results.</li> <li>Advance the minimum required version of "flex" from 2.5.4 to 2.5.31, and update documentation accordingly. This is required in order to have support for a reentrant scanner. I'm committing this bit separately in order to have an easy reference if we later decide to make the minimum something different (like 2.5.33).</li> <li>Convert the core lexer and parser into fully reentrant code, by making use of features added to flex and bison since this code was originally written. This change doesn't in itself offer any new capability, but it's needed infrastructure for planned improvements in plpgsql. Another feature now available in flex is the ability to make it use palloc instead of malloc, so do that to avoid possible memory leaks. (We should at some point change the other lexers likewise, but this commit doesn't touch them.)</li> <li>In pgsql/src/backend/parser/scan.l, although the flex documentation avers that yyalloc and yyrealloc take size_t arguments, the emitted scanner actually prototypes them with type yy_size_t, which is sometimes not the same thing depending on flex version and platform. Easiest fix seems to be to use yy_size_t. Per buildfarm results.</li> <li>Make the configure messages rejecting old bison and flex versions include the full path and version of the program being rejected.</li> </ul> <p>Heikki Linnakangas a commit&eacute;&nbsp;:</p> <ul> <li>In pgsql/src/backend/utils/adt/formatting.c, fix ancient bug in handling of to_char modifier 'TH', when used with Hitoshi Harada. In what seems like an oversight, we used to treat 'TH' the same as lowercase 'th', but only with HH/HH12.</li> <li>In pgsql/src/backend/utils/init/postinit.c, need to use pg_perm_setlocale when setting LC_CTYPE and LC_COLLATE at startup. Otherwise, the LC_CTYPE/COLLATE setting gets reverted when using plperl, which leads to incorrect query results and index corruption. This was accidentally broken in the per-database locale patch in 8.4. Pointed out by Andrew (RhodiumToad) Gierth.</li> </ul> <p>Bruce Momjian a commit&eacute;&nbsp;:</p> <ul> <li>Stamp minor library version numbers for 8.5; sorry for the delay.</li> </ul> <p><strong>Correctifs rejet&eacute;s (&agrave; ce jour)</strong></p> <ul> <li>Pas de d&eacute;ception cette semaine&nbsp;:-)</li> </ul> <p><strong>Correctifs en attente</strong></p> <ul> <li>Fujii Masao sent a WIP patch to introduce a new value, sync_file_range, to wal_sync_method.</li> <li>Heikki Linnakangas sent in a WIP patch to set client_encoding automatically from locale in libpq.</li> <li>Pavel Stehule sent in a patch to fix BUG #4907: stored procedures and changed tables.</li> <li>ITAGAKI Takahiro sent in two patches to parallelize pgbench.</li> <li>Robert Haas sent in three patches to help fix the issue around the *_collapse_limit GUC parameters.</li> <li>Josh Tolley sent in a patch against the Commitfest code to keep Perl::Critic quiet.</li> <li>Peter Eisentraut sent in two revisions of a patch to allow byteas to be escaped for input and output as hex.</li> <li>KaiGai Kohei sent in another revision of his SE-PostgreSQL patches.</li> <li>Brendan Jurd sent in another revision of the patch to add scientific notation to to_char().</li> <li>Bernd Helmle sent in another revision of a patch to allow for dropping columns and constraints conditionally.</li> <li>Tom Lane sent in a patch to increase the minimum flex version in order to enable a reentrant parser.</li> <li>Dean Rasheed sent in two WIP patches to allow deferrable unique constraints.</li> <li>Marko (johto) Tiikkaja sent in a patch to allow INSERT...RETURNING inside a CTE.</li> <li>Andrew (RhodiumToad) Gierth sent in a patch to update hstore to CVS TIP.</li> <li>Teodor Sigaev sent in a patch to fix wrong algorithms for "contains" and "overlaps" operations over polygons, including regression tests for same.</li> <li>Jaime Casanova sent in an update to Mark Kirkwood's patch which adds lock wait statistics to the pg_catalog, including a new view.</li> </ul>