Nouvelles hebdomadaires de PostgreSQL - 19 mai 2013
Si vous assistez à la PGCon cette année, n'hésitez pas à soumettre une proposition pour un lightning talk : http://lists.pgcon.org/pipermail/pgcon-announce/2013-May/000100.html
PGDay UK 2013 est à présent ouvert aux inscriptions : http://postgresqlusergroup.org.uk
L'appel à conférenciers pour le pgconf.eu 2013 est lancé : http://2013.pgconf.eu/
Offres d'emplois autour de PostgreSQL en mai
- Internationales : http://archives.postgresql.org/pgsql-jobs/2013-05/threads.php;
- Francophones : http://forums.postgresql.fr/viewforum.php?id=4.
PostgreSQL Local
- PGCon 2013 aura lieu les 23 & 24 mai 2013 à l'Université d'Ottawa : http://www.pgcon.org/2013/
- Premier rassemblement utilisateurs/développeurs Postgres-XC après le Cluster Summit : https://wiki.postgresql.org/wiki/PgCon2013CanadaClusterSummit#PostgresXC_Summit
- La 6ème conférence annuelle "Prague PostgreSQL Developers Day", organisée par le CSPUG (Groupe des utilisateurs tchèques et slovaques de PostgreSQL), aura lieu le 30 mai 2013 à la Faculté des Sciences Mathématiques & Physiques de l'Université Charles (Malostranske namesti 25, Prague). Les candidatures des conférenciers sont attendues jusqu'au 14 avril à l'adresse <info AT p2d2 POINT cz>. D'avantage d'informations sur le site : http://www.p2d2.cz/
- Le PgDay Fr est l'événement majeur de la communauté francophone. Il aura lieu le 13 juin 2013 à Nantes (France) : http://pgday.fr/
- PostgreSQL Brazil aura lieu du 15 au 17 août 2013 à Porto Velho, État du Rondônia au Brésil : http://pgbr.postgresql.org.br/2013/chamada.en.php
- Notez la date ! Postgres Open 2013 aura lieu à Chicago (Illinois, USA) du 16 au 18 septembre. Hotel Sax :
https://reservations.ihotelier.com/crs/g_reservation.cfm?groupID=888761&hotelID=6865
Inscriptions pour les lève-tôt : http://postgresopen-eac2.eventbrite.com/ - La PGConf.EU 2013 sera tenue du 29 octobre au 1er novembre au Conrad Hotel dans le centre-ville de Dublin en Irlande : http://2013.pgconf.eu/
- PGConf.DE 2013 aura lieu le 8 novembre 2013 au musée industriel de la Rhénanie à Oberhausen : http://2013.pgconf.de/
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 poussé :
- Fix handling of OID wraparound while in standalone mode. If OID wraparound should occur while in standalone mode (unlikely but possible), we want to advance the counter to FirstNormalObjectId not FirstBootstrapObjectId. Otherwise, user objects might be created with OIDs in the system-reserved range. That isn't immediately harmful but it poses a risk of conflicts during future pg_upgrade operations. Noted by Andres Freund. Back-patch to all supported branches, since all of them are supported sources for pg_upgrade operations. http://git.postgresql.org/pg/commitdiff/e9c336c78638c191642b18628c306d1c1573fb12
- Allow CREATE FOREIGN TABLE to include SERIAL columns. The behavior is that the required sequence is created locally, which is appropriate because the default expression will be evaluated locally. Per gripe from Brad Nicholson that this case was refused with a confusing error message. We could have improved the error message but it seems better to just allow the case. Also, remove ALTER TABLE's arbitrary prohibition against being applied to foreign tables, which was pretty inconsistent considering we allow it for views, sequences, and other relation types that aren't even called tables. This is needed to avoid breaking pg_dump, which sometimes emits column defaults using separate ALTER TABLE commands. (I think this can happen even when the default is not associated with a sequence, so that was a pre-existing bug once we allowed column defaults for foreign tables.) http://git.postgresql.org/pg/commitdiff/b14206862278347a379f2bb72d92d16fb9dcea45
- Fix some uses of "the quick brown fox". If we're going to quote a well-known pangram, we should quote it accurately. Per gripe from Thom Brown. http://git.postgresql.org/pg/commitdiff/e7bfc7e42cebf80507f9c9965dc4a572e9fb76a4
- Fix fd.c to preserve errno where needed. PathNameOpenFile failed to ensure that the correct value of errno was returned to its caller after a failure (because it incorrectly supposed that free() can never change errno). In some cases this would result in a user-visible failure because an expected ENOENT errno was replaced with something else. Bogus EINVAL failures have been observed on OS X, for example. There were also a couple of places that could mangle an important value of errno if FDDEBUG was defined. While the usefulness of that debug support is highly debatable, we might as well make it safe to use, so add errno save/restore logic to the DO_DB macro. Per bug #8167 from Nelson Minar, diagnosed by RhodiumToad. Back-patch to all supported branches. http://git.postgresql.org/pg/commitdiff/6563fb2b45146852601e63828308fe04fb03b9e9
- Fix crash when trying to display a NOTIFY rule action. Fixes oversight in commit 2ffa740be9d96a3743ecb7e42391c53d0760c65a. Per report from Josh Kupershmidt. I think we've broken this case before, so let's add a regression test this time. http://git.postgresql.org/pg/commitdiff/403bd6a18b8ec5aeee51c08360441c3c3c239d8f
- Clarify documentation of EXPLAIN (TIMING OFF) option. Clarify that this option doesn't suppress measurement of the statement's total runtime. Greg Smith http://git.postgresql.org/pg/commitdiff/2af0971f35a4a7b87312b83782d9bb0cc6a40ad0
Peter Eisentraut a poussé :
- doc: Fix order of options on pgbench man page http://git.postgresql.org/pg/commitdiff/bd1710248795a495547a96f16d16592ad45f6943
- doc: Fix some whitespace issues in the man pages http://git.postgresql.org/pg/commitdiff/a9bb274f902987b271e2f0dd844fb610de4f024b
- pg_upgrade: Replace tabs in output string constants by spaces http://git.postgresql.org/pg/commitdiff/d2b920cded4db973a7b69a628e109f2aee63012a
- doc: Add \dm command to psql man page http://git.postgresql.org/pg/commitdiff/a2a480af889b5d9abce4181e49b6398f0e24b808
Bruce Momjian a poussé :
- release docs: mention PL/pgSQL as supporting event triggers in PG 9.3 http://git.postgresql.org/pg/commitdiff/f472012a3257d022dd36c6b5e30ad8d223d0ccea
Heikki Linnakangas a poussé :
- Remove unused regression test files. euc_* and mule_internal test cases were identical to the ones in src/test/mb. sql_ascii didn't exist elsewhere, but has been broken since 2001, and doesn't seem very interesting anyway. drop.sql hasn't been used since 2000, when regress.sh was removed. http://git.postgresql.org/pg/commitdiff/d0cab7903bf695bf305bd4c01f99e0e28d233d91
Simon Riggs a poussé :
- Remove single space on end of a line in xlog.c. Michael Paquier http://git.postgresql.org/pg/commitdiff/c94dff4c3c18595a9d6d8a97020145c1155de473
- Emit msg correctly for timeline-crossing crash http://git.postgresql.org/pg/commitdiff/1781744cfcfeed6e3ad2e4d52dbd475a95be03a0
- Init crash recovery using the latest available TLI. This simplifies the handling of crashes after fast promotion and various minor cases that can exist in short timing windows around that case. Broad fix to bug reported by Michael Paquier on -hackers, approach prompted by Heikki Linnakangas http://git.postgresql.org/pg/commitdiff/d4337a0dcbd29e5b11c2157f808916de62de05e4
Correctifs rejetés (à ce jour)
- No one was disappointed this week
Correctifs en attente
- Noah Misch sent in a patch to implement MemoryContextAllocHuge() and repalloc_huge()
- Peter Geoghegan sent in a patch to ensure that all "loaded library..." messages are DEBUG1, regardless of whether local_preload_libraries or shared_preload_libraries is involved, and regardless of EXEC_BACKEND.
- Robins Tharakan sent in a patch to add more tests for ASYNC.
- Heikki Linnakangas sent in a patch to improve LWLocks by using compare-and-swap CPU instructions where available.
- Peter Eisentraut sent in a patch to make psql delay setting up its cancel handler until after a database connection is established.
- Mark Kirkwood sent in a patch to add pg_stat_get_changes_since_analyze() and associated columns to system views.
- Amit Kapila sent in two revisions of a patch to move unused buffers to freelist.
- Maciej Gajewski sent in a patch to cache and query result histories in psql.
- Peter Geoghegan sent in another revision of a patch to replace our quicksort_arg with timsort_arg.
- Amit Langote sent four patches intended to allow logging PAM auth failure.
- Jon Nelson sent in three more revisions of a patch to use fallocate where available, reducing the time it takes to write a WAL file.
- Dean Rasheed sent in a patch to ensure that views atop writeable foreign tables are writeable along with changes to catalog views showing foreign tables' writeability.
- Amul Sul sent in a patch to add a connection request wait time to psql.
- Cedric Villemain sent in a WIP patch to fix a case where 9.3 breaks extensions.
- Heikki Linnakangas sent in a patch to fix a quoting issue in pg_basebackup.
- Joe Abbate sent in a patch to fix an issue in the release notes about DROP TABLE ... IF EXISTS.
- Dan Farina sent in a set of patches to enrich the auth mechanism in libpq.
- Greg Smith sent in a WIP patch to track block write statistics.
- Chris Farmiloe sent in a patch to hook the privilege system to LISTEN/NOTIFY.