Nouvelles hebdomadaires de PostgreSQL - 8 mai 2011
PostgreSQL 9.1 beta 1 est disponible. À vos tests !
http://www.postgresql.org/developer/beta
L'AustinPUG se réunira le 11 mai à 19h à Austin (Texas, États-Unis d'amérique). Pizza gratuite ! Pour être nourri, RSVP à austinpug AT postgresql DOT org :
http://pugs.postgresql.org/austinpug
CHAR(11), la conférence PostgreSQL sur le clustering, la haute disponibilité et la réplication accepte à présent les inscriptions et réservations. Dates : 11 & 12 juillet 2011 à Cambridge, Royaume-Uni :
http://www.char11.org/
PostgreSQL Conference West (#PgWest) aura lieu du 27 au 30 septembre 2011 au centre des conventions de San Jose (Californie, États-Unis) :
http://www.postgresqlconference.org
Les nouveautés des produits dérivés
Offres d'emplois autour de PostgreSQL en mai
PostgreSQL Local
PostgreSQL dans les média
PostgreSQL Weekly News / les nouvelles hebdomadaires vous sont offertes cette semaine par David Fetter. Traduction par l'équipe PostgreSQLFr sous licence CC BY-NC-SA.
Proposez vos articles ou annonces avant dimanche 15:00 (heure du Pacifique). Merci de les envoyer en anglais à david (a) fetter.org, en allemand à pwn (a) pgug.de, en italien à pwn (a) itpug.org et en espagnol à pwn (a) arpug.com.ar.
(lien vers l'article original)
Revues de code
Correctifs appliqués
Tom Lane a poussé :
- Improve aset.c's space management in contexts with small maxBlockSize. The previous coding would allow requests up to half of maxBlockSize to be treated as "chunks", but when that actually did happen, we'd waste nearly half of the space in the malloc block containing the chunk, if no smaller requests came along to fill it. Avoid this scenario by limiting the maximum size of a chunk to 1/8th maxBlockSize, so that we can waste no more than 1/8th of the allocated space. This will not change the behavior at all for the default context size parameters (with large maxBlockSize), but it will change the behavior when using ALLOCSET_SMALL_MAXSIZE. In particular, there's no longer a need for spell.c to be overly concerned about the request size parameters it uses, so remove a rather unhelpful comment about that. Merlin Moncure, per an idea of Tom Lane's
http://git.postgresql.org/pg/commitdiff/6755558b92748287e961fed518c14be375630464
- Fix pull_up_sublinks' failure to handle nested pull-up opportunities. After finding an EXISTS or ANY sub-select that can be converted to a semi-join or anti-join, we should recurse into the body of the sub-select. This allows cases such as EXISTS-within-EXISTS to be optimized properly. The original coding would leave the lower sub-select as a SubLink, which is no better and often worse than what we can do with a join. Per example from Wayne Conrad. Back-patch to 8.4. There is a related issue in older versions' handling of pull_up_IN_clauses, but they're lame enough anyway about the whole area that it seems not worth the extra work to try to fix.
http://git.postgresql.org/pg/commitdiff/dcc685debb02c507b88aa8052f9e6334a7c3f830
- Include unary plus in the Operator Precedence table. Per gripe from Grzegorz Szpetkowski. Also, change the subsection heading from "Lexical Precedence" (which is a contradiction in terms) to "Operator Precedence".
http://git.postgresql.org/pg/commitdiff/671322751add80f3368cd9ef17134fb9f73cf747
- Remove precedence labeling of keywords TRUE, FALSE, UNKNOWN, and ZONE. These were labeled with precedences just to avoid attaching explicit precedences to the productions in which they were the last terminal symbol. Since a terminal symbol precedence marking can affect many other things too, it seems like better practice to attach precedence labels to the productions, and not mark the terminal symbols. Ideally we'd also remove the precedence attached to NULL_P, but it turns out that we are actually depending on that having a precedence higher than POSTFIXOP, else we get a shift/reduce conflict for postfix operators in b_expr. (Which more or less proves my point about these markings having a high risk of unexpected consequences.) For the moment, move NULL_P into the set of keywords grouped with IDENT, so that at least it will act similarly to non-keywords; and document the interaction.
http://git.postgresql.org/pg/commitdiff/12b7164578e73abb065a835c588c1e0c44670ed3
- Move RegisterPredicateLockingXid() call to a safer place. The SSI patch inserted a call of RegisterPredicateLockingXid into GetNewTransactionId, which was a bad idea on a couple of grounds. First, it's not necessary to hold XidGenLock while manipulating that shared memory, and doing so is bad because XidGenLock is a high-contention lock that should be held for as short a time as possible. (Not to mention that it adds an entirely unnecessary deadlock hazard, since we must take SerializableXactHashLock as well.) Second, the specific place where it was put was between extending CLOG and advancing nextXid, which could result in unpleasant behavior in case of a failure there. Pull the call out to AssignTransactionId, which is much safer and arguably better from a modularity standpoint too. There is more work to do to clean up the failure-before-advancing-nextXid issue, but that is a separate change that will need to be back-patched. So for the moment I just want to make GetNewTransactionId look the same as it did in prior versions.
http://git.postgresql.org/pg/commitdiff/d2088ae949993ad8e3aabc3b6a9cd77aa5cac957
- Fix some portability issues in isolation regression test driver. Remove random system #includes in favor of using postgres_fe.h. (The alternative to that is letting this module grow its own configuration testing ability...) Also fix the "make clean" target to actually clean things up. Per local testing.
http://git.postgresql.org/pg/commitdiff/eff223ffd74eed268f35d693462969f7f75632d2
Peter Eisentraut a poussé :
Alvaro Herrera a poussé :
Bruce Momjian a poussé :
Magnus Hagander a poussé :
Robert Haas a poussé :
Correctifs rejetés (à ce jour)
- Pas de déception cette semaine :-)
Correctifs en attente
- Gabriele Bartolini sent in another revision of the patch to smooth replication during VACUUM FULL.
- Joe Conway sent in a patch to fix clog redos under high load.
- Johann 'Myrkraverk' Oskarsson sent in a patch to fix an issue on mingw-w64 where the PGDLLEXPORT macro is blank.
- Alvaro Herrera updated the "preferred types" patch to HEAD.
- Jaime Casanova sent in a patch to add an xlogversion column to IDENTIFY_SYSTEM. This is one of the infrastructure pieces which will make on-line upgrades possible.
- Hitoshi Harada sent in a patch to allow the optimizer to pull up aggregate subqueries.
- Bruce Momjian sent in patches to adjust the comments on system tables.
- Magnus Hagander sent in a patch to fix the error for attempting to index a foreign table.
- Tom Lane sent in a patch to fix a some suprising precedence in PostgreSQL's SQL grammar.
- Dan Ports sent in two revisions of a patch to fix a race condition in SSI's ChecTargetForConflictsIn.
- Peter Geoghegan sent in a WIP patch to help save energy by waking up less frequently.
- Merlin Moncure sent in another revision of the patch to fix an issue between the visibility map and hint bits.
- Robert Haas sent in another revision of the patch to make visibility maps more crash-safe.
- Josh Kupershmidt sent in a patch to clean up psql's decribe.c.
- Andrew Dunstan sent in another revision of the patch to fix an issue where invalid characters were allowed in XML.
- Greg Smith sent in a patch exemplifying the idea of moving some contrib modules to being default, but still using the EXTENSION infrastructure.