Nouvelles hebdomadaires de PostgreSQL - 11 septembre 2011
L'appel à conférenciers a été lancé pour le FLOSS UK, programmé du 20 au 22 mars 2012 à Edimbourg. La date limite de dépôt des candidatures est fixée au 18 novembre 2011 et les conférenciers sélectionnés seront informés avant le 25 novembre. Les propositions sont à envoyer à postgresql2012 AT flossuk POINT org. Plus d'informations via le lien suivant :
http://www.flossuk.org/Events/Spring2012
Nouveau sondage : Quand pensez-vous mettre à jour vers la 9.1 ?
http://www.postgresql.org/community
Le PUG de New-York présente "PostgreSQL 9.1 Overview" avec Bruce Momjian à 18h30, le 22 septembre au Yodle. RSVP et détails ci-après :
http://www.nycpug.org/events/32571952/
[ndt: sortie de PostgreSQL 9.1, la dépêche en français :
http://blog.postgresql.fr/index.php?post/2011/09/12/Sortie-de-PostgreSQL-9.0]
Les nouveautés des produits dérivés
Offres d'emplois autour de PostgreSQL en septembre
PostgreSQL Local
- Postgres Open 2011, conférence ayant pour thème les évolutions brutales dans l'industrie de la base de données, aura lieu du 14 au 16 septembre 2011 à Chicago (Illinois, États-Unis) à l'hôtel "Westin Michigan Avenue" :
http://postgresopen.org
- PostgreSQL Conference West (#PgWest) aura lieu du 27 au 30 septembre 2011 au centre des conventions de San José (Californie, États-Unis) :
http://www.postgresqlconference.org
- La "PostgreSQL Conference Europe 2011" se tiendra à Amsterdam, du 18 au 21 octobre :
http://2011.pgconf.eu/
- Le PG-Day Denver 2011 aura lieu le vendredi 21 octobre 2011 dans le campus Auraria près de Denver, Colorado :
http://pgday.consistentstate.com/
- pgbr aura lieu à São Paulo (Brésil) les 3 & 4 novembre 2011 :
http://pgbr.postgresql.org.br/
- PGConf.DE 2011 est une conférence germanophone tenue le 11 novembre au musée industriel du Rhin à Oberhausen (Allemagne). L'appel à conférenciers est lancé :
http://2011.pgconf.de/
- La cinquième édition du PGDay italien (PGDay.IT 2011) aura lieu le 25 novembre à Prato :
http://2011.pgday.it/
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
Bruce Momjian a poussé :
Tom Lane a poussé :
- Update time zone data files to tzdata release 2011i. DST law changes in Canada, Egypt, Russia, Samoa, South Sudan.
http://git.postgresql.org/pg/commitdiff/0b88af150e3a26f9e41da89da0c507eac550e46b
- Update type-conversion documentation for long-ago changes. This example wasn't updated when we changed the behavior of bpcharlen() in 8.0, nor when we changed the number of parameters taken by the bpchar() cast function in 7.3. Per report from lsliang.
http://git.postgresql.org/pg/commitdiff/b7f83e70d9758c5dd480c9dbba1668ddeec37916
- Add an "incompatibility" entry to 9.1 release notes about CREATE EXTENSION. We've now seen more than one gripe from somebody who didn't get the memo about how to install contrib modules in 9.1. Try to make it a little more prominent that you aren't supposed to call the scripts directly anymore.
http://git.postgresql.org/pg/commitdiff/ae92eff6b93c6ee18ca5c48958c355f5a448f8f5
- Avoid possibly accessing off the end of memory in examine_attribute(). Since the last couple of columns of pg_type are often NULL, sizeof(FormData_pg_type) can be an overestimate of the actual size of the tuple data part. Therefore memcpy'ing that much out of the catalog cache, as analyze.c was doing, poses a small risk of copying past the end of memory and incurring SIGSEGV. No such crash has been identified in the field, but we've certainly seen the equivalent happen in other code paths, so patch this one all the way back. Per valgrind testing by Noah Misch, though this is not his proposed patch. I chose to use SearchSysCacheCopy1 rather than inventing special-purpose infrastructure for copying only the minimal part of a pg_type tuple.
http://git.postgresql.org/pg/commitdiff/780a342c900fa085e8c065b3282b491de69ab10d
- Avoid possibly accessing off the end of memory in SJIS2004 conversion. The code in shift_jis_20042euc_jis_2004() would fetch two bytes even when only one remained in the string. Since conversion functions aren't supposed to assume null-terminated input, this poses a small risk of fetching past the end of memory and incurring SIGSEGV. No such crash has been identified in the field, but we've certainly seen the equivalent happen in other code paths, so patch this one all the way back. Report and patch by Noah Misch.
http://git.postgresql.org/pg/commitdiff/623f77e9d1338720512430a0b8e824d7359739b8
- Improve comment about handling of temp tables in shared-inval code.
http://git.postgresql.org/pg/commitdiff/db10f01baa2148f1773cacfcbadc7158ae94c081
- Fix get_name_for_var_field() to deal with RECORD Params. With 9.1's use of Params to pass down values from NestLoop join nodes to their inner plans, it is possible for a Param to have type RECORD, in which case the set of fields comprising the value isn't determinable by inspection of the Param alone. However, just as with a Var of type RECORD, we can find out what we need to know if we can locate the expression that the Param represents. We already knew how to do this in get_parameter(), but I'd overlooked the need to be able to cope in get_name_for_var_field(), which led to EXPLAIN failing with "record type has not been registered". To fix, refactor the search code in get_parameter() so it can be used by both functions. Per report from Marti Raudsepp.
http://git.postgresql.org/pg/commitdiff/a7d9203cc4edfbcc283732efea6d54db0399ccee
- Fix typo in error message. Per Euler Taveira de Oliveira.
http://git.postgresql.org/pg/commitdiff/99155aaa33f417daabd38c8b225c09a3c6da71ba
- Fix corner case bug in numeric to_char(). Trailing-zero stripping applied by the Fujii Masao specifier could strip zeroes to the left of the decimal point, for a format with no digit positions after the decimal point (such as "FM999."). Reported and diagnosed by Marti Raudsepp, though I didn't use his patch.
http://git.postgresql.org/pg/commitdiff/f0bedf3e456c52274995d32d4c0c8a250de5c1ca
- One last round of copy-editing for the 9.1 release notes. Also set the documented release date to 2011-09-12.
http://git.postgresql.org/pg/commitdiff/09b68c70af855a0a69cede14da70968ddd97ba05
- round() is not portable. Use rint().
http://git.postgresql.org/pg/commitdiff/d63de337f3e235f02d79a1df79dddbb002e9fd4e
- Stamp 9.1.0.
http://git.postgresql.org/pg/commitdiff/1f43001424a9da624a89b213d0be606a8212a50a
- Move Timestamp/Interval typedefs and basic macros into datatype/timestamp.h. As per my recent proposal, this refactors things so that these typedefs and macros are available in a header that can be included in frontend-ish code. I also changed various headers that were undesirably including utils/timestamp.h to include datatype/timestamp.h instead. Unsurprisingly, this showed that half the system was getting utils/timestamp.h by way of xlog.h. No actual code changes here, just header refactoring.
http://git.postgresql.org/pg/commitdiff/a7801b62f21bd051444bd1119cd3745ecc8e14ec
- Simplify handling of the timezone GUC by making initdb choose the default. We were doing some amazingly complicated things in order to avoid running the very expensive identify_system_timezone() procedure during GUC initialization. But there is an obvious fix for that, which is to do it once during initdb and have initdb install the system-specific default into postgresql.conf, as it already does for most other GUC variables that need system-environment-dependent defaults. This means that the timezone (and log_timezone) settings no longer have any magic behavior in the server. Per discussion.
http://git.postgresql.org/pg/commitdiff/ca4af308c32d03db5fbacb54d6e583ceb904f268
- Try to un-break MSVC build. I thought we had enough infrastructure to absorb CPPFLAGS changes from the makefiles, but buildfarm says otherwise.
http://git.postgresql.org/pg/commitdiff/5a8de2f2e7fd5d2265f30206743ba2dd51bff222
- Fix permissions on pg_largeobject_metadata.h in 9.0 branch. For some reason it was 0755 instead of 0644.
http://git.postgresql.org/pg/commitdiff/4de174d4bfa8e162cf64fb9bf7393fea05b0dee7
- Remove no-longer-used variable.
http://git.postgresql.org/pg/commitdiff/5f42e5945b3dd96c228531c0730f418846ced04e
- Invent a new memory context primitive, MemoryContextSetParent. This function will be useful for altering the lifespan of a context after creation (for example, by creating it under a transient context and later reparenting it to belong to a long-lived context). It costs almost no new code, since we can refactor what was there. Per my proposal of yesterday.
http://git.postgresql.org/pg/commitdiff/b0025bd95703aaedc4ff23ddcfbde9597fa0919d
Peter Eisentraut a poussé :
Alvaro Herrera a poussé :
Simon Riggs a poussé :
Heikki Linnakangas a poussé :
ITAGAKI Takahiro a poussé :
Correctifs rejetés (à ce jour)
- Pas de déception cette semaine :-)
Correctifs en attente
- Heikki Linnakangas and Alexander Korotkov traded new versions of the patch to build GiST indexes quickly.
- Oleg Bartunov sent in three more revisions of the patch to implement space-partitioned GiST indexes.
- Marti Raudsepp sent in another revision of the patch to generate more useful column names for subquery expressions.
- Marti Raudsepp sent in a patch which adds the backend's current running query to the "backend crash" message.
- Shigeru HANADA sent in two more revisions of a patch to add a "force not null" option to the file FDW.
- Pavan Deolasee sent in another revision of the patch to a single-pass VACUUM.
- Fujii Masao sent in two revisions of a patch to add a pg_last_xact_insert_timestamp.
- Marko (johto) Tiikkaja sent in a patch to add an nfiltered annotation to EXPLAIN.
- George Barnett sent in a patch intended to improve the way PostgreSQL runs with NFS data directory on Linux.
- Tom Lane sent in a WIP patch to bring ECPG in line with the rest of the code, which as of this week has a separate header for the core timestamp definitions and macros.
- Fujii Masao sent in a patch to unite recovery.conf with postgres.conf.
- Fujii Masao sent in two revisions of a patch to add a replication option to the createuser utility.
- Alexey Klyukin sent in another revision of the patch to allow the pg config parser to continue on error.
- Marti Raudsepp sent in a patch to cache constant stable expressions per execution.
- Josh Kupershmidt sent in another revision of the patch to allow \dd to show constraint names.
- Jun Ishiduka sent in another revision of the patch to make it possible to take an on-line base backup from a hot standby.
- Andrew Dunstan sent in a patch intended to fix the issue where the databse super-user is presumed to be a member of every role.
- Alexander Korotkov sent in another revision of the patch implementing a double-sorting picksplit implementation for GiST indexes.
- KaiGai Kohei sent in another flock of patches reworking DROP into a single unified framework.