Le PUG de Londres se réunira le 11 septembre pour discuter du nouveau PostgreSQL 9.3 : http://www.postgresql.org/about/event/1615/

La quatrième édition du PGDay argentin se tiendra le 14 novembre 2013 à Buenos Aires, Argentine. L'appel à conférenciers est lancé : http://wiki.postgresql.org/wiki/PGDay_Argentina_2013

Le PGDay cubain aura lieu en novembre 2013 : http://postgresql.uci.cu/

Les nouveautés des produits dérivés

Offres d'emplois autour de PostgreSQL en septembre

PostgreSQL Local

  • Postgres Open 2013 aura lieu à Chicago, (USA, Illinois) du 16 au 18 septembre : http://postgresopen.org/
  • Open Source Software for Business (OSS4B) 2013 aura lieu à Prato (Toscane, Italie) les 19 & 20 septembre. Les inscriptions sont ouvertes : http://www.oss4b.it/
  • La PostgreSQL Conference China de 2103 aura lieu les 26 & 27 octobre à Hangzhou. Informations : https://wiki.postgresql.org/wiki/Pgconf_cn2013
    Inscriptions : http://bbs.pgsqldb.com/client/bm.php
  • Le PGDay italien (PGDay.IT) sera tenu à Prato (Italie, Toscane) au centre de recherche de l'Université Monash. Inscriptions et infos : http://2013.pgday.it
  • La PGConf.EU 2013 sera tenue du 29 octobre au 1er novembre au Conrad Hotel dans le centre-ville de Dublin en Irlande. Les inscriptions sont ouvertes : http://2013.pgconf.eu/
  • PGConf.DE 2013 aura lieu le 8 novembre 2013 au musée industriel de la Rhénanie à Oberhausen. L'appel à conférenciers porte jusqu'au 15 septembre : http://2013.pgconf.de/

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

Peter Eisentraut a poussé :

Andrew Dunstan a poussé :

Tom Lane a poussé :

  • Update time zone data files to tzdata release 2013d. DST law changes in Israel, Morocco, Palestine, Paraguay. Historical corrections for Macquarie Island. http://git.postgresql.org/pg/commitdiff/79daaa3e812c7600ef30ef3e6ba5e75cab18f212
  • Docs: wording improvements in discussion of timestamp arithmetic. I started out just to fix the broken markup in commit 1c2085766187031eaeaae7db4785b9e1d4241988, but got distracted by copy-editing. I see Bruce already fixed the markup, but I'll commit the wordsmithing anyway. http://git.postgresql.org/pg/commitdiff/7489eb4d3b7fef2c2eaeb66e3bcb3fb74385b44d
  • Don't fail for bad GUCs in CREATE FUNCTION with check_function_bodies off. The previous coding attempted to activate all the GUC settings specified in SET clauses, so that the function validator could operate in the GUC environment expected by the function body. However, this is problematic when restoring a dump, since the SET clauses might refer to database objects that don't exist yet. We already have the parameter check_function_bodies that's meant to prevent forward references in function definitions from breaking dumps, so let's change CREATE FUNCTION to not install the SET values if check_function_bodies is off. Authors of function validators were already advised not to make any "context sensitive" checks when check_function_bodies is off, if indeed they're checking anything at all in that mode. But extend the documentation to point out the GUC issue in particular. (Note that we still check the SET clauses to some extent; the behavior with !check_function_bodies is now approximately equivalent to what ALTER DATABASE/ROLE have been doing for awhile with context-dependent GUCs.) This problem can be demonstrated in all active branches, so back-patch all the way. http://git.postgresql.org/pg/commitdiff/546f7c2e38531469eb3cff62256fde8606330c67
  • Allow aggregate functions to be VARIADIC. There's no inherent reason why an aggregate function can't be variadic (even VARIADIC ANY) if its transition function can handle the case. Indeed, this patch to add the feature touches none of the planner or executor, and little of the parser; the main missing stuff was DDL and pg_dump support. It is true that variadic aggregates can create the same sort of ambiguity about parameters versus ORDER BY keys that was complained of when we (briefly) had both one- and two-argument forms of string_agg(). However, the policy formed in response to that discussion only said that we'd not create any built-in aggregates with varying numbers of arguments, not that we shouldn't allow users to do it. So the logical extension of that is we can allow users to make variadic aggregates as long as we're wary about shipping any such in core. In passing, this patch allows aggregate function arguments to be named, to the extent of remembering the names in pg_proc and dumping them in pg_dump. You can't yet call an aggregate using named-parameter notation. That seems like a likely future extension, but it'll take some work, and it's not what this patch is really about. Likewise, there's still some work needed to make window functions handle VARIADIC fully, but I left that for another day. initdb forced because of new aggvariadic field in Aggref parse nodes. http://git.postgresql.org/pg/commitdiff/0d3f4406dfa00d848711fdb4af53be663ffc7d0f
  • Update comments concerning PGC_S_TEST. This GUC context value was once only used by ALTER DATABASE SET and ALTER USER SET. That's not true anymore, though, so rewrite the comments to be a bit more general. Patch in HEAD only, since this is just an internal documentation issue. http://git.postgresql.org/pg/commitdiff/0c66a223774dec62edb5281a47e72fe480a8f7aa

Heikki Linnakangas a poussé :

  • Fix typo in comment. Also line-wrap an over-wide line in a comment that's ignored by pgindent. http://git.postgresql.org/pg/commitdiff/a93bdfc711399716328ce0811d600411b1314306
  • Keep heavily-contended fields in XLogCtlInsert on different cache lines. Performance testing shows that if the insertpos_lck spinlock and the fields that it protects are on the same cache line with other variables that are frequently accessed, the false sharing can hurt performance a lot. Keep them apart by adding some padding. http://git.postgresql.org/pg/commitdiff/375d8526f2900d0c377f44532f6d09ee06531f67
  • Make catalog cache hash tables resizeable. If the hash table backing a catalog cache becomes too full (fillfactor > 2), enlarge it. A new buckets array, double the size of the old, is allocated, and all entries in the old hash are moved to the right bucket in the new hash. This has two benefits. First, cache lookups don't get so expensive when there are lots of entries in a cache, like if you access hundreds of thousands of tables. Second, we can make the (initial) sizes of the caches much smaller, which saves memory. This patch dials down the initial sizes of the catcaches. The new sizes are chosen so that a backend that only runs a few basic queries still won't need to enlarge any of them. http://git.postgresql.org/pg/commitdiff/20cb18db4668b016748fbb5fcb1422bc3e0d52d1

Gregory Stark a poussé :

Robert Haas a poussé :

Bruce Momjian a poussé :

Alvaro Herrera a poussé :

Jeff Davis a poussé :

Kevin Grittner a poussé :

  • Eliminate pg_rewrite.ev_attr column and related dead code. Commit 95ef6a344821655ce4d0a74999ac49dd6af6d342 removed the ability to create rules on an individual column as of 7.3, but left some residual code which has since been useless. This cleans up that dead code without any change in behavior other than dropping the useless column from the catalog. http://git.postgresql.org/pg/commitdiff/277607d600fb71e25082b94302ca1716403cd0bc

Noah Misch a poussé :

Michael Meskes a poussé :

Correctifs rejetés (à ce jour)

  • No one was disappointed this week

Correctifs en attente

  • Fabrízio de Royes Mello sent in another revision of a patch to add SEQUENCES to the possible arguments of DISCARD.
  • Dimitri Fontaine sent in another revision of a patch to implement extension templates.
  • Karl O. Pinc sent in another revision of a patch to clarify backup instructions and concepts in the documentation.
  • Maksym Boguk sent in a patch to add a national character type.
  • Cedric Villemain sent in a patch to fix the way PGXS works for certain extension builds.
  • Antonin Houska sent in another revision of a patch to allow throttling pg_basebackup.
  • Takayuki Tsunakawa sent in a patch to clarify the recovery documentation as it relates to preserving statistics.
  • Blake Smith sent in two more revisions of a patch intended to speed up queries which use a GIN index.
  • Bruce Momjian sent in two more revisions of a patch to fix some NULL handling.
  • Bruce Momjian sent in a patch to make a default effective_cache_size based on the shared_buffers setting.
  • Zoltan Boszormenyi sent in two more revisions of a patch to use readahead in ECPG FETCHes.
  • Pavel Stehule sent in another revision of a patch to improve NUMERIC performance.
  • Hari Babu sent in a patch to optimize WAL updates on systems with certain access profiles.
  • Andres Freund sent in another revision of a patch to speed up catalog cache lookups.
  • Andres Freund, as part of the infrastructure for logical change replication, sent in a pair of patches to: 1. Allow walsenders to connect to a specific database, and 2. Log xl_running_xact's at a higher frequency than checkpoints are done.
  • Andres Freund, as part of the infrastructure for logical change replication, sent in a patch to add information about a table's primary key to the RelationData struct.
  • Andres Freund, as part of the infrastructure for logical change replication, sent in a patch to introduce the concept and usage of InvalidCommandId.
  • Mitsumasa KONDO sent in a WIP patch to use the FALLOC_FL_KEEP_SIZE flag where appropriate.
  • KaiGai Kohei sent in a patch to create infrastructure for custom plan nodes.
  • Satoshi Nagayasu sent in another revision of a patch to add statistics tracking for dirty writes.
  • MauMau sent in a patch to set the codeset for libc catalog the same as postgres catalog to ensure that errors don't appear in the form '???', which is singularly unhelpful.
  • Bruce Momjian sent in a patch to correct the permissions used in information_schema.schemata.
  • Alexander Korotkov sent in two revisions of a patch to fix how picksplit works in the case of NaN values.