L'appel à conférenciers pour le Char(13) et le PGday UK, respectivement les 11 et 12 juillet 2013, sont lancés et seront clos le 19 avril 2013. Pour le Char(13), écrivez à speakers AT char13 DOT info ; pour le PGday UK, speakers AT postgresqlusergroup DOT org DOT uk.

Les nouveautés des produits dérivés

Offres d'emplois autour de PostgreSQL en mars

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)

Correctifs appliqués

Simon Riggs a poussé :

Tom Lane a poussé :

  • Improve documentation of EXTRACT(WEEK). The docs showed that early-January dates can be considered part of the previous year for week-counting purposes, but failed to say explicitly that late-December dates can also be considered part of the next year. Fix that, and add a cross-reference to the "isoyear" field. Per bug #7967 from Pawel Kobylak. http://git.postgresql.org/pg/commitdiff/e39feb1006ac5c64fd804597088bc7f40ff7b635
  • Bump up timeout delays some more in timeouts isolation test. The buildfarm members using -DCLOBBER_CACHE_ALWAYS still don't like this test. Some experimentation shows that on my machine, isolationtester's query to check for "waiting" state takes 2 to 2.5 seconds to bind+execute under -DCLOBBER_CACHE_ALWAYS. Set the timeouts to 5 seconds to leave some headroom for possibly-slower buildfarm critters. Really we ought to fix the "waiting" query, which is not only horridly slow but outright wrong in detail; and then maybe we can back off these timeouts. But right now I'm just trying to get the buildfarm green again. http://git.postgresql.org/pg/commitdiff/a7921f71a3c747141344d8604f6a6d7b4cddb2a9
  • Redo postgres_fdw's planner code so it can handle parameterized paths. I wasn't going to ship this without having at least some example of how to do that. This version isn't terribly bright; in particular it won't consider any combinations of multiple join clauses. Given the cost of executing a remote EXPLAIN, I'm not sure we want to be very aggressive about doing that, anyway. In support of this, refactor generate_implied_equalities_for_indexcol so that it can be used to extract equivalence clauses that aren't necessarily tied to an index. http://git.postgresql.org/pg/commitdiff/9cbc4b80ddc10b36c64514104caa69747c386dcf
  • Avoid retrieving dummy NULL columns in postgres_fdw. This should provide some marginal overall savings, since it surely takes many more cycles for the remote server to deal with the NULL columns than it takes for postgres_fdw not to emit them. But really the reason is to keep the emitted queries from looking quite so silly ... http://git.postgresql.org/pg/commitdiff/e690b9515072fd7767fdeca5c54166f6a77733bc
  • Update commit_delay documentation. Commit 13fe298ca06f5390df5edf073cf401f9f0b67458 changed this GUC to be PGC_SUSET, but neglected to update the documentation to match. While at it, edit and rearrange the text a little for clarity. http://git.postgresql.org/pg/commitdiff/82b945c0979350c87ddc52adefe9f0a36dd5b4c8
  • Suppress uninitialized-variable warning in new checksum code. Some compilers understand that this coding is safe, and some don't. http://git.postgresql.org/pg/commitdiff/4912385b56afe68ef76e47d38df1d61ada0fde2f
  • Fix contrib/dblink to handle inconsistent DateStyle/IntervalStyle safely. If the remote database's settings of these GUCs are different from ours, ambiguous datetime values may be read incorrectly. To fix, temporarily adopt the remote server's settings while we ingest a query result. This is not a complete fix, since it doesn't do anything about ambiguous values in commands sent to the remote server; but there seems little we can do about that end of it given dblink's entirely textual API for transmitted commands. Back-patch to 9.2. The hazard exists in all versions, but this patch would need more work to apply before 9.2. Given the lack of field complaints about this issue, it doesn't seem worth the effort at present. Daniel Farina and Tom Lane http://git.postgresql.org/pg/commitdiff/8a3b6772aedbd95557ab1fc489ddf007ac9d405d
  • Document cross-version compatibility issues for contrib/postgres_fdw. One of the use-cases for postgres_fdw is extracting data from older PG servers, so cross-version compatibility is important. Document what we can do here, and further annotate some of the coding choices that create compatibility constraints. In passing, remove one unnecessary incompatibility with old servers, namely assuming that we didn't need to quote the timezone name 'UTC'. http://git.postgresql.org/pg/commitdiff/5b86fedfb57ea943f883a13c6d50c5a9e2a1cc57
  • Don't put <indexterm> before <term> in <varlistentry> items. Doing that results in a broken index entry in PDF output. We had only a few like that, which is probably why nobody noticed before. Standardize on putting the <term> first. Josh Kupershmidt http://git.postgresql.org/pg/commitdiff/cdc67938c086104ef7a0e2f1e6912e9ee0ba4c85
  • Update time zone abbreviation lists for changes missed since 2006. Most (all?) of Russia has moved to what's effectively year-round daylight savings time, so that the "standard" zone names now mean an hour later than they used to. Update that, notably changing MSK as per recent complaint from Sergey Konoplev, but also CHOT, GET, IRKT, KGT, KRAT, MAGT, NOVT, OMST, VLAT, YAKT, YEKT. The corresponding DST abbreviations are presumably now obsolete, but I left them in place with their old definitions, just to reduce any possible breakage from this change. Also add VOLT (Europe/Volgograd), which for some reason we never had before, as well as MIST (Antarctica/Macquarie), and fix obsolete definitions of MAWT, TKT, and WST. http://git.postgresql.org/pg/commitdiff/3b91fe185a71c05ac4528f93a39ba27232acc9e0
  • Semi-automatically detect changes in timezone abbreviations. Add an option to zic.c to dump out all non-obsolete timezone abbreviations defined in the Olson database. Comparing this list to its previous state will clue us in when something happens that we may need to account for in the tznames/ time zone abbreviation lists. The README file's previous exhortation to "just grep for differences" was completely useless advice, in my now-considerable experience; but maybe this will be a bit more useful. As a starting point I built the same list from the tzdata files as they existed in 2006, which is committed here as known_abbrevs.txt. Comparison indeed turned up quite a few changes we had neglected to account for, which I will commit separately. http://git.postgresql.org/pg/commitdiff/69602772700e62b7b03e3f0ac7b10aa651c0c998
  • Fix some unportable constructs in parallel pg_dump code. Didn't compile on semi-obsolete gcc, and probably not on not-gcc-at-all either. http://git.postgresql.org/pg/commitdiff/846681fdd574548d4f430f2ff7ab44d77b4c79fe

Kevin Grittner a poussé :

Alvaro Herrera a poussé :

  • Allow extracting machine-readable object identity Introduce pg_identify_object(oid,oid,int4), which is similar in spirit to pg_describe_object but instead produces a row of machine-readable information to uniquely identify the given object, without resorting to OIDs or other internal representation. This is intended to be used in the event trigger implementation, to report objects being operated on; but it has usefulness of its own. Catalog version bumped because of the new function. http://git.postgresql.org/pg/commitdiff/f8348ea32ec8d713cd6e5d5e16f15edef22c4d03

Heikki Linnakangas a poussé :

  • Fix "element <@ range" cost estimation. The statistics-based cost estimation patch for range types broke that, by incorrectly assuming that the left operand of all range oeprators is a range. That lead to a "type x is not a range type" error. Because it took so long for anyone to notice, add a regression test for that case. We still don't do proper statistics-based cost estimation for that, so you just get a default constant estimate. We should look into implementing that, but this patch at least fixes the regression. Spotted by Tom Lane, when testing query from Josh Berkus. http://git.postgresql.org/pg/commitdiff/f897c4744fea221dfc7bbd277081edad41d1d58d

Andrew Dunstan a poussé :

Correctifs rejetés (à ce jour)

  • No one was disappointed this week

Correctifs en attente

  • Robins Tharakan sent in three more revisions of a patch to add regression tests for SCHEMA-related commands.
  • Pavel Stehule and Hadi Moshayedi traded patches to optimize avg() and friends on NUMERIC.
  • Hadi Moshayedi sent in a patch to add infrastructure which helps the above optimization, namely an aggtransspace parameter used in creating aggregate functions which approximates the size of the aggregate function's internal transition (a.k.a. state) data.
  • Steve Singer and Bruce Momjian traded patches to fix an infelicity in the handling of wrong PGSERVICE entries.
  • Nicholas White sent in four more revisions of a patch to add the ability to ignore NULLs in windowing functions per the SQL standard.
  • Michael Paquier sent in three revisions of a patch to ensure that pg_dump only dumps valid indexes.
  • Zoltan Boszormenyi sent in another revision of a patch to fix an infelicity in lock_timeout on Windows.
  • Ants Aasma sent in three revisions of a patch to implement slice-by-8 checksums on x86_64 CPUs.
  • KaiGai Kohei sent in another revision of a patch to implement OAT_POST_ALTER object access hooks.
  • Robins Tharakan sent in a patch to increase the regression tests' coverage of the ROLE code.
  • KaiGai Kohei sent in another revision of a patch to implement row-level access control.
  • Daniele Varazzo sent in some patches to fix strings for error messages in git master.
  • Alvaro Herrera sent in another revision of the dropped_objects patch vs. event triggers.
  • Brendan Jurd sent in a patch to disallow 0-dimensional arrays.
  • Andrew Dunstan sent in another revision of a patch to fix some hstore compiler warnings.
  • Alvaro Herrera sent in another revision of a patch to ensure that autovacuum sets priority on vacuums intended to prevent XID wraparound.
  • Michael Paquier sent in two revisions of a patch to ensure that custom bgworkers receive SIGHUP if the postmaster is notified.
  • Alexander Korotkov sent in another revision of a patch to make certain (DFA) regexep searches indexable.
  • Kevin Grittner sent in a patch intended to correct certain situations where pg_dump produced different results on subsequent runs from the first after a reload.
  • Adriano Lange sent in a patch to add a new optimizer, Sampling and Dynamic Programming (SDP), to PostgreSQL.
  • Michael Paquier sent in another revision of a patch to implement REINDEX CONCURRENTLY.
  • Xi Wang sent in a patch to avoid a buffer underflow in errfinish().
  • Michael Paquier sent in another revision of a patch to overhaul recovery.conf.