Communauté francophone de PostgreSQL

Cette page est en lecture seule. Vous pouvez afficher le texte source, mais ne pourrez pas le modifier. Contactez votre administrateur si vous pensez qu'il s'agit d'une erreur.
<html>
<p><strong>Nouvelles hebdomadaires de PostgreSQL - 20 mars 2011</strong></p>
<p>PostgreSQL a &eacute;t&eacute; accept&eacute; comme mentor pour le <em>Google Summer of Code</em> 2011&nbsp;! Si vous &ecirc;tes &eacute;tudiant et que vous &ecirc;tes int&eacute;ress&eacute;, les candidatures sont accept&eacute;es jusqu'au 28 mars 2011. D&eacute;tails et id&eacute;es par ici&nbsp;: 
<a target="_blank" href="http://wiki.postgresql.org/wiki/GSoC_2011">http://wiki.postgresql.org/wiki/GSoC_2011</a></p>
<p><strong>Les nouveaut&eacute;s des produits d&eacute;riv&eacute;s</strong></p>
<ul>
<li>bucardo 4.4.2, un syst&egrave;me de r&eacute;plication pour PostgreSQL, released: 
<a target="_blank" href="http://bucardo.org/wiki/Bucardo">http://bucardo.org/wiki/Bucardo</a></li>
<li>tail_n_mail 1.17.6, un outil de surveillance des logs&nbsp;: 
<a target="_blank" href="http://bucardo.org/wiki/Tail_n_mail">http://bucardo.org/wiki/Tail_n_mail</a></li>
</ul>
<p><strong>Offres d'emplois autour de PostgreSQL en mars</strong></p>
<ul>
<li>Internationales&nbsp;: 
<a target="_blank" href="http://archives.postgresql.org/pgsql-jobs/2011-03/threads.php">http://archives.postgresql.org/pgsql-jobs/2011-03/threads.php</a>;</li>
<li>Francophones&nbsp;: 
<a target="_blank" href="http://forums.postgresql.fr/viewforum.php?id=4">http://forums.postgresql.fr/viewforum.php?id=4</a>.</li>
</ul>
<p><strong>PostgreSQL Local</strong></p>
<ul>
<li>PostgreSQL Conference East 2011&nbsp;: New-York City, du 22 au 25 mars&nbsp;: 
<a target="_blank" href="http://www.postgresqlconference.org">http://www.postgresqlconference.org</a></li>
<li>PostgreSQL aura une pr&eacute;sence importante lors de la "<em>MySQL Conference and Expo</em>", du 11 au 14 avril &agrave; Santa Clara (Californie)&nbsp;: 
<a target="_blank" href="http://en.oreilly.com/mysql2011/public/schedule/tag/postgresql">http://en.oreilly.com/mysql2011/public/schedule/tag/postgresql</a></li>
<li>L'<em>Open Database Camp</em> aura lieu du 7 au 9 mai 2011 en Sardaigne (Italie)&nbsp;: 
<a target="_blank" href="http://datacharmer.blogspot.com/2011/01/announcing-open-database-camp-sardinia.html">http://datacharmer.blogspot.com/2011/01/announcing-open-database-camp-sardinia.html</a></li>
<li>PGCon aura lieu les 19 &amp; 20 mai 2011 &agrave; l'Universit&eacute; d'Ottawa, pr&eacute;c&eacute;d&eacute; par deux jours de tutoriels les 17 &amp; 18 mai&nbsp;: 
<a target="_blank" href="http://www.pgcon.org/2011/">http://www.pgcon.org/2011/</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. 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 et en espagnol &agrave; pwn (a) arpug.com.ar.</i></p>
<p>(<a target="_blank" href="http://www.postgresql.org/community/weeklynews/pwn20110320">lien vers l'article original</a>)</p>
<p><strong>Revues de code</strong></p>
<p><strong>Correctifs appliqu&eacute;s</strong></p>
<p>Bruce Momjian a pouss&eacute;&nbsp;:</p>
<ul>
<li>Remove duplicate time-based macros recently added. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/b051a34fd8877635186ed84a857f2f38cd059468">http://git.postgresql.org/pg/commitdiff/b051a34fd8877635186ed84a857f2f38cd059468</a></li>
<li>Add database comments to template0 and postgres databases, and improve the comments on the template1 database. No catalog version bump because they are just comments. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/ddd6ff289f2512f881493b7793853a96955459ff">http://git.postgresql.org/pg/commitdiff/ddd6ff289f2512f881493b7793853a96955459ff</a></li>
<li>Wording adjustment for restart_after_crash entry Specifically, mention that "restart" is disabled by this parameter. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/df4a9595c20ccd3d3b4ce0e638ca1a5e82546a97">http://git.postgresql.org/pg/commitdiff/df4a9595c20ccd3d3b4ce0e638ca1a5e82546a97</a></li>
<li>Fix spelling error in fuzzystrmatch docs. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/b774efa9d57a02fbd64dafbe55a059253fbfda4e">http://git.postgresql.org/pg/commitdiff/b774efa9d57a02fbd64dafbe55a059253fbfda4e</a></li>
<li>Add hint suggesting the use of EXECUTE CREATE TABLE ... AS for EXECUTE INTO. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/2b8364de698b0b425e5d8631a63c91387ee098ef">http://git.postgresql.org/pg/commitdiff/2b8364de698b0b425e5d8631a63c91387ee098ef</a></li>
<li>Adjust doc wording about the casting exceptions for composite types. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/a858ca19df1491a5082864335efb0fe08e27e960">http://git.postgresql.org/pg/commitdiff/a858ca19df1491a5082864335efb0fe08e27e960</a></li>
<li>Remove unused copy_dir() function from pg_upgrade. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/898a14e1a0ba845c957f42f205495af932fcf017">http://git.postgresql.org/pg/commitdiff/898a14e1a0ba845c957f42f205495af932fcf017</a></li>
<li>Document guc context values, and reference them from the config doc section. Tom Lane. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/e148443ddd95cd29edf4cc1de6188eb9cee029c5">http://git.postgresql.org/pg/commitdiff/e148443ddd95cd29edf4cc1de6188eb9cee029c5</a></li>
<li>Document the all-balls IPv6 address. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/a7136b7fa2505ec209210803bb74a7946ede337f">http://git.postgresql.org/pg/commitdiff/a7136b7fa2505ec209210803bb74a7946ede337f</a></li>
<li>Document that the timestamp returned by pg_last_xact_replay_timestamp is the time on the primary that the transaction was generated. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/0191e120e6b427f16aed239c657b9e32c83a0f6d">http://git.postgresql.org/pg/commitdiff/0191e120e6b427f16aed239c657b9e32c83a0f6d</a></li>
<li>Remove "all balls" mention of network address; change IPv6 address to ::/0. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/56bb7f2a0275c5e7f17f8fba0d93d12a471869a4">http://git.postgresql.org/pg/commitdiff/56bb7f2a0275c5e7f17f8fba0d93d12a471869a4</a></li>
<li>Initial version of PostgreSQL 9.1 release notes. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/b03b17c4118345cc89dda1d96cda9ed2313f3ed9">http://git.postgresql.org/pg/commitdiff/b03b17c4118345cc89dda1d96cda9ed2313f3ed9</a></li>
<li>Add SGML markup for keywords, terms, functions, commands, etc. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/025f4c72f029242a6aaf3f14bb6d7da4ce070f72">http://git.postgresql.org/pg/commitdiff/025f4c72f029242a6aaf3f14bb6d7da4ce070f72</a></li>
<li>Add links to documentation from 9.1 release notes. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/b2c5b3d1753f1a3e5cb68a610bda27ad768bf061">http://git.postgresql.org/pg/commitdiff/b2c5b3d1753f1a3e5cb68a610bda27ad768bf061</a></li>
<li>Move PITR and StreamingRep up one level of heading in the 9.1 release notes. Remove excessive linking to pg_ctl manual page. Reorder incompatibility sections. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/c2f4ea469b52e6f7fedff651a4aa0acced873a5f">http://git.postgresql.org/pg/commitdiff/c2f4ea469b52e6f7fedff651a4aa0acced873a5f</a></li>
<li>Reorder some 9.1 release item documentation entries, fix some awkward wording. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/f670c195b64a97b8b9e9780e80614cd03b9fcadd">http://git.postgresql.org/pg/commitdiff/f670c195b64a97b8b9e9780e80614cd03b9fcadd</a></li>
<li>Fix snapshot isolation level typo in 9.1 release notes. Thom Brown 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/e8f4c240c7065edcbe82e06a2d86c05c8abee67f">http://git.postgresql.org/pg/commitdiff/e8f4c240c7065edcbe82e06a2d86c05c8abee67f</a></li>
<li>Another 9.1 release note typo fix. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/78fce29628f99a7dd002561dc87904456c992173">http://git.postgresql.org/pg/commitdiff/78fce29628f99a7dd002561dc87904456c992173</a></li>
<li>Markup and wording improvements for 9.1 release notes. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/62bf9c28061c614df530ac672b1e59f88e805578">http://git.postgresql.org/pg/commitdiff/62bf9c28061c614df530ac672b1e59f88e805578</a></li>
</ul>
<p>Tom Lane a pouss&eacute;&nbsp;:</p>
<ul>
<li>Adjust regression test to avoid platform-dependent failure. We have a test that verifies that max(anyarray) will cope if the array column elements aren't all the same array type. However, it's now possible for that to produce a collation-related error message instead of the expected one, if the first two column elements happen to be of the same type and it's one that expects to be given collation info. Tweak the test to ensure this doesn't happen. Per buildfarm member pika. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/f12423d75a1181d75bd646869b140ba0c199fa99">http://git.postgresql.org/pg/commitdiff/f12423d75a1181d75bd646869b140ba0c199fa99</a></li>
<li>Improve handling of unknown-type literals in UNION/INTERSECT/EXCEPT. This patch causes unknown-type Consts to be coerced to the resolved output type of the set operation at parse time. Formerly such Consts were left alone until late in the planning stage. The disadvantage of that approach is that it disables some optimizations, because the planner sees the set-op leaf query as having different output column types than the overall set-op. We saw an example of that in a recent performance gripe from Claudio Freire. Fixing such a Const requires scribbling on the leaf query in transformSetOperationTree, but that should be all right since if the leaf query's semantics depended on that output column, it would already have resolved the unknown to something else. Most of the bulk of this patch is a simple adjustment of transformSetOperationTree's API so that upper levels can get at the TargetEntry containing a Const to be replaced: it now returns a list of TargetEntries, instead of just the bare expressions. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/72cfc17aef4fc9aa2de1c82045b7d609c0f2c513">http://git.postgresql.org/pg/commitdiff/72cfc17aef4fc9aa2de1c82045b7d609c0f2c513</a></li>
<li>Revise collation derivation method and expression-tree representation. All expression nodes now have an explicit output-collation field, unless they are known to only return a noncollatable data type (such as boolean or record). Also, nodes that can invoke collation-aware functions store a separate field that is the collation value to pass to the function. This avoids confusion that arises when a function has collatable inputs and noncollatable output type, or vice versa. Also, replace the parser's on-the-fly collation assignment method with a post-pass over the completed expression tree. This allows us to use a more complex (and hopefully more nearly spec-compliant) assignment rule without paying for it in extra storage in every expression node. Fix assorted bugs in the planner's handling of collations by making collation one of the defining properties of an EquivalenceClass and by converting CollateExprs into discardable RelabelType nodes during expression preprocessing. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/b310b6e31ce5aa9e456c43c0e8e93248b0c84c02">http://git.postgresql.org/pg/commitdiff/b310b6e31ce5aa9e456c43c0e8e93248b0c84c02</a></li>
<li>Fix up handling of C/POSIX collations. Install just one instance of the "C" and "POSIX" collations into pg_collation, rather than one per encoding. Make these instances exist and do something useful even in machines without locale_t support: to wit, it's now possible to force comparisons and case-folding functions to use C locale in an otherwise non-C database, whether or not the platform has support for using any additional collations. Fix up severely broken upper/lower/initcap functions, too: the C/POSIX fastpath now does what it is supposed to, and non-default collations are handled correctly in single-byte database encodings. Merge the two separate collation hashtables that were being maintained in pg_locale.c, and be more wary of the possibility that we fail partway through filling a cache entry. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/176d5bae1d636fc1e91840b12cbd04c96d638b7e">http://git.postgresql.org/pg/commitdiff/176d5bae1d636fc1e91840b12cbd04c96d638b7e</a></li>
<li>Suppress platform-dependent unused-variable warning. The local variable "sock" can be unused depending on compilation flags. But there seems no particular need for it, since the kernel calls can just as easily say port-&gt;sock instead. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/82e4d45bd0ba9c07b8a97f28f939db6d8d564f9a">http://git.postgresql.org/pg/commitdiff/82e4d45bd0ba9c07b8a97f28f939db6d8d564f9a</a></li>
<li>Add some platform-independent tests for the collation feature. There's a lot we can't test very well without platform dependencies, but the C/POSIX collations should now work the same way everywhere. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/9b095fbea4d6e80e3288e08bd2af4f33aa66875e">http://git.postgresql.org/pg/commitdiff/9b095fbea4d6e80e3288e08bd2af4f33aa66875e</a></li>
</ul>
<p>Magnus Hagander a pouss&eacute;&nbsp;:</p>
<ul>
<li>Remove special case allowing parameters to ident auth for initdb. This was required in pre-8.4 versions to allow the specification of "ident sameuser", but sameuser is no longer required. It could be extended to allow all parameters in the future, but should then apply to all methods and not just ident. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/01c1a12a5bb4d4f837a542c187ebb2719f9334e8">http://git.postgresql.org/pg/commitdiff/01c1a12a5bb4d4f837a542c187ebb2719f9334e8</a></li>
<li>Properly clear the verbose output of pg_basebackup. Don't leave partial filename information on the last status or dangling characters if the previous filename was longer than the current one. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/4a0014806d909bbb490f568af0b8f1ede06149ed">http://git.postgresql.org/pg/commitdiff/4a0014806d909bbb490f568af0b8f1ede06149ed</a></li>
<li>Rename ident authentication over local connections to peer. This removes an overloading of two authentication options where one is very secure (peer) and one is often insecure (ident). Peer is also the name used in libpq from 9.1 to specify the same type of authentication. Also make initdb select peer for local connections when ident is chosen, and ident for TCP connections when peer is chosen. ident keyword in pg_hba.conf is still accepted and maps to peer authentication. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/6f9192df61e183826211ad2eaf325c6de5cf3656">http://git.postgresql.org/pg/commitdiff/6f9192df61e183826211ad2eaf325c6de5cf3656</a></li>
<li>Misc minor fixes to 9.1 release notes. Thom Brown 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/0f96ae643c5815d14e39ae8d349be218aae126a8">http://git.postgresql.org/pg/commitdiff/0f96ae643c5815d14e39ae8d349be218aae126a8</a></li>
</ul>
<p>Robert Haas a pouss&eacute;&nbsp;:</p>
<ul>
<li>Remove 13 keywords that are used only for ROLE options. Review by Tom Lane. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/5ca4dfc79f21828174de3a8bc7d29718d0c52c34">http://git.postgresql.org/pg/commitdiff/5ca4dfc79f21828174de3a8bc7d29718d0c52c34</a></li>
<li>Minor sync rep documentation improvements: Make the name of the ID tag for the GUC entry match the GUC name; Clarify that synchronous_replication waits for xlog flush, not receipt; Mention that synchronous_replication won't wait if max_wal_senders=0. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/f0f3617135854281bdb79179a895c102d54cb95b">http://git.postgresql.org/pg/commitdiff/f0f3617135854281bdb79179a895c102d54cb95b</a></li>
<li>Corrections to CREATE FOREIGN TABLE documentation. Omit incorrect = sign, and properly document server_name parameter. Shigeru Hanada. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/5f588e20051eb18333f6ea5b46bd779ba1eb8773">http://git.postgresql.org/pg/commitdiff/5f588e20051eb18333f6ea5b46bd779ba1eb8773</a></li>
<li>Tab completion for \pset format and \pset linestyle. Pavel Stehule 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/ad3aff45f0d302b35d009e525de8a9d0ee9745a9">http://git.postgresql.org/pg/commitdiff/ad3aff45f0d302b35d009e525de8a9d0ee9745a9</a></li>
<li>Tab completion for \pset format and \pset linestyle. Pavel Stehule 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/ad3aff45f0d302b35d009e525de8a9d0ee9745a9">http://git.postgresql.org/pg/commitdiff/ad3aff45f0d302b35d009e525de8a9d0ee9745a9</a></li>
<li>Fix various possible problems with synchronous replication. 1. Don't ignore query cancel interrupts. Instead, if the user asks to cancel the query after we've already committed it, but before it's on the standby, just emit a warning and let the COMMIT finish. 2. Don't ignore die interrupts (pg_terminate_backend or fast shutdown). Instead, emit a warning message and close the connection without acknowledging the commit. Other backends will still see the effect of the commit, but there's no getting around that; it's too late to abort at this point, and ignoring die interrupts altogether doesn't seem like a good idea. 3. If synchronous_standby_names becomes empty, wake up all backends waiting for synchronous replication to complete. Without this, someone attempting to shut synchronous replication off could easily wedge the entire system instead. 4. Avoid depending on the assumption that if a walsender updates MyProc-&gt;syncRepState, we'll see the change even if we read it without holding the lock. The window for this appears to be quite narrow (and probably doesn't exist at all on machines with strong memory ordering) but protecting against it is practically free, so do that. 5. Remove useless state SYNC_REP_MUST_DISCONNECT, which isn't needed and doesn't actually do anything. There's still some further work needed here to make the behavior of fast shutdown plausible, but that looks complex, so I'm leaving it for a separate commit. Review by Fujii Masao. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/9a56dc3389b9470031e9ef8e45c95a680982e01a">http://git.postgresql.org/pg/commitdiff/9a56dc3389b9470031e9ef8e45c95a680982e01a</a></li>
<li>Add pause_at_recovery_target to recovery.conf.sample; improve docs. Fujii Masao, but with the proposed behavior change reverted, and the rest adjusted accordingly. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/84abea76f60c5fd1c008b8ddf250b4bc89e288fc">http://git.postgresql.org/pg/commitdiff/84abea76f60c5fd1c008b8ddf250b4bc89e288fc</a></li>
<li>Remove bogus comment. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/02b1f84e7d2c8921d3ef291469cfd4b7235358f0">http://git.postgresql.org/pg/commitdiff/02b1f84e7d2c8921d3ef291469cfd4b7235358f0</a></li>
<li>Protocol documentation for Hot Standby feedback messages. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/76dbb4615389e1f44e48074b87be77262143021e">http://git.postgresql.org/pg/commitdiff/76dbb4615389e1f44e48074b87be77262143021e</a></li>
<li>Minor fixes for high availability documentation. Erik Rijkers and me. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/f94c6f9c0f05ff70b232e620eb9c420294e90cd3">http://git.postgresql.org/pg/commitdiff/f94c6f9c0f05ff70b232e620eb9c420294e90cd3</a></li>
<li>Remove bogus semicolons in recoveryPausesHere. Without this, the startup process goes into a tight loop, consuming 100% of one CPU and failing to respond to interrupts. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/777e8c0015743224cc46f3ce39243b05c6d882ef">http://git.postgresql.org/pg/commitdiff/777e8c0015743224cc46f3ce39243b05c6d882ef</a></li>
<li>Remove ancient -X options to pg_dump, pg_dumpall, pg_restore. The last version in which these options were documented is now EOL, so it's time to get rid of them for real. We now use GNU-style long options instead. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/c5eb835bbffb99518405a1e5bccb58c85e0ab30e">http://git.postgresql.org/pg/commitdiff/c5eb835bbffb99518405a1e5bccb58c85e0ab30e</a></li>
<li>Make synchronous replication query cancel/die messages more consistent. Per a gripe from Thom Brown about my previous commit in this area, commit 9a56dc3389b9470031e9ef8e45c95a680982e01a. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/7a37900443b016e0e7c72f6b42327bc05f8b5003">http://git.postgresql.org/pg/commitdiff/7a37900443b016e0e7c72f6b42327bc05f8b5003</a></li>
<li>Woops. Previous patch to remove -X options missed getopt_long calls(). Noted by Tom Lane. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/f78ba0a73a60f40270b21c4582f6a7d52fe16739">http://git.postgresql.org/pg/commitdiff/f78ba0a73a60f40270b21c4582f6a7d52fe16739</a></li>
<li>Move synchronous_standbys_defined updates from WAL writer to BG writer. This is advantageous because the BG writer is alive until much later in the shutdown sequence than WAL writer; we want to make sure that it's possible to shut off synchronous replication during a smart shutdown, else it might not be possible to complete the shutdown at all. Per very reasonable gripes from Fujii Masao and Simon Riggs. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/727589995a3e027046f0da7af6ba665b0b47f89f">http://git.postgresql.org/pg/commitdiff/727589995a3e027046f0da7af6ba665b0b47f89f</a></li>
<li>Fix possible "tuple concurrently updated" error in ALTER TABLE. When adding an inheritance parent to a table, an AccessShareLock on the parent isn't strong enough to prevent trouble, so take ShareUpdateExclusiveLock instead. Since this is a behavior change, albeit a fairly unobtrusive one, and since we have only one report from the field, no back-patch. Report by Jon Nelson, analysis by Alvaro Herrera, fix by me. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/fbcf4b92aa64d4577bcf25925b055316b978744a">http://git.postgresql.org/pg/commitdiff/fbcf4b92aa64d4577bcf25925b055316b978744a</a></li>
</ul>
<p>Andrew Dunstan a pouss&eacute;&nbsp;:</p>
<ul>
<li>Use correct PATH separator for Cygwin in pg_regress.c. This has been broken for years, and I'm not sure why it has not been noticed before, but now a very modern Cygwin breaks on it, and the fix is clearly correct. Backpatching to all live branches. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/5b079cb248b91cbd5bc577ea96802ec466f40b38">http://git.postgresql.org/pg/commitdiff/5b079cb248b91cbd5bc577ea96802ec466f40b38</a></li>
</ul>
<p>Peter Eisentraut a pouss&eacute;&nbsp;:</p>
<ul>
<li>Raise maximum value of several timeout parameters The maximum value of deadlock_timeout, max_standby_archive_delay, max_standby_streaming_delay, log_min_duration_statement, and log_autovacuum_min_duration was INT_MAX/1000 milliseconds, which is about 35min, which is too short for some practical uses. Raise the maximum value to INT_MAX; the code that uses the parameters already supports that just fine. 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/8c0a5eb78af00ec4720e693feaba70b5a73205d1">http://git.postgresql.org/pg/commitdiff/8c0a5eb78af00ec4720e693feaba70b5a73205d1</a></li>
</ul>
<p>Alvaro Herrera a pouss&eacute;&nbsp;:</p>
<ul>
<li>Fix PL/Python memory leak involving array slices. Report and patch from Daniel Popowich, bug #5842 (with some debugging help from Alex Hunsaker) 
<a target="_blank" href="http://git.postgresql.org/pg/commitdiff/1c249fcfcc331d589a2fa1574e16c0ef3d1547ce">http://git.postgresql.org/pg/commitdiff/1c249fcfcc331d589a2fa1574e16c0ef3d1547ce</a></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 in another revision of the replication server timeout patch.</li>
<li>Robert Haas sent in two revisions of a patch intended to fix some infelicities in syncrep.</li>
<li>Roman Zotov sent in a patch to turn PREFERRED for type from a boolean to an int2, which allows for an expression of precedence.</li>
<li>Thom Brown sent in a patch to allow users to set a default database name other than postgres in initdb.</li>
<li>Piyush Newe sent in a patch intended to fix some infelicities in century handling in to_date.</li>
<li>Heikki Linnakangas sent in another revision of the patch to enable taking multiple base backups.</li>
<li>Radoslaw Smogura sent in two revisions of a patch to add a second level buffer cache.</li>
<li>Kevin Grittner sent in two revisions of a patch intended to fix an issue in SSI.</li>
<li>Nikhil Sontakke sent in two revisions of a patch to fix an issue with a VACUUM FULL deadlock.</li>
<li>Jan Urbanski sent in another revision of the patch to add PL/PythonU tracebacks.</li>
</ul>
</html>
Communauté francophone de PostgreSQL

Outils pour utilisateurs

Outils du site

Outils de la page
