Les nouveautés des produits dérivés

Offres d'emplois autour de PostgreSQL en août

PostgreSQL Local

  • Postgres Open 2013 aura lieu à Chicago, (USA, Illinois) du 16 au 18 septembre : http://postgresopen.org/
  • Le PGDay italien (PGDay.IT) sera tenu à Prato (Italie, Toscane) au centre de recherche de l'Université Monash. Un appel international à conférenciers est lancé : http://2013.pgday.it/index.php/programma/call-for-papers-english/
  • La PGConf.EU 2013 sera tenue du 29 octobre au 1er novembre au Conrad Hotel dans le centre-ville de Dublin en Irlande. L'appel à conférenciers est lancé : 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

Bruce Momjian a poussé :

Tom Lane a poussé :

  • Emit a log message if output is about to be redirected away from stderr. We've seen multiple cases of people looking at the postmaster's original stderr output to try to diagnose problems, not realizing/remembering that their logging configuration is set up to send log messages somewhere else. This seems particularly likely to happen in prepackaged distributions, since many packagers patch the code to change the factory-standard logging configuration to something more in line with their platform conventions. In hopes of reducing confusion, emit a LOG message about this at the point in startup where we are about to switch log output away from the original stderr, providing a pointer to where to look instead. This message will appear as the last thing in the original stderr output. (We might later also try to emit such link messages when logging parameters are changed on-the-fly; but that case seems to be both noticeably harder to do nicely, and much less frequently a problem in practice.) Per discussion, back-patch to 9.3 but not further. http://git.postgresql.org/pg/commitdiff/3d5282c6f0edbdcb78dd2a6e8068f829fcb2882f
  • Remove ph_may_need from PlaceHolderInfo, with attendant simplifications. The planner logic that attempted to make a preliminary estimate of the ph_needed levels for PlaceHolderVars seems to be completely broken by lateral references. Fortunately, the potential join order optimization that this code supported seems to be of relatively little value in practice; so let's just get rid of it rather than trying to fix it. Getting rid of this allows fairly substantial simplifications in placeholder.c, too, so planning in such cases should be a bit faster. Issue noted while pursuing bugs reported by Jeremy Evans and Antonin Houska, though this doesn't in itself fix either of their reported cases. What this does do is prevent an Assert crash in the kind of query illustrated by the added regression test. (I'm not sure that the plan for that query is stable enough across platforms to be usable as a regression test output ... but we'll soon find out from the buildfarm.) Back-patch to 9.3. The problem case can't arise without LATERAL, so no need to touch older branches. http://git.postgresql.org/pg/commitdiff/1b1d3d92c3ec1179c65756f60a1eb477793488ea
  • Fix planner problems with LATERAL references in PlaceHolderVars. The planner largely failed to consider the possibility that a PlaceHolderVar's expression might contain a lateral reference to a Var coming from somewhere outside the PHV's syntactic scope. We had a previous report of a problem in this area, which I tried to fix in a quick-hack way in commit 4da6439bd8553059766011e2a42c6e39df08717f, but Antonin Houska pointed out that there were still some problems, and investigation turned up other issues. This patch largely reverts that commit in favor of a more thoroughly thought-through solution. The new theory is that a PHV's ph_eval_at level cannot be higher than its original syntactic level. If it contains lateral references, those don't change the ph_eval_at level, but rather they create a lateral-reference requirement for the ph_eval_at join relation. The code in joinpath.c needs to handle that. Another issue is that createplan.c wasn't handling nested PlaceHolderVars properly. In passing, push knowledge of lateral-reference checks for join clauses into join_clause_is_movable_to. This is mainly so that FDWs don't need to deal with it. This patch doesn't fix the original join-qual-placement problem reported by Jeremy Evans (and indeed, one of the new regression test cases shows the wrong answer because of that). But the PlaceHolderVar problems need to be fixed before that issue can be addressed, so committing this separately seems reasonable. http://git.postgresql.org/pg/commitdiff/9e7e29c75ad441450f9b8287bd51c13521641e3b
  • Fix thinko in comment. http://git.postgresql.org/pg/commitdiff/f1d5fce7cf11d596b2617a5696fd8eb5ebff2b33

Peter Eisentraut a poussé :

Kevin Grittner a poussé :

Magnus Hagander a poussé :

Heikki Linnakangas a poussé :

Robert Haas a poussé :

Correctifs rejetés (à ce jour)

  • No one was disappointed this week

Correctifs en attente

  • Dean Rasheed sent in a WIP patch to extend auto-updatable views to support views containing a mix of updatable and non-updatable columns. This is basically the "columns" part of SQL Feature T111, "Updatable joins, unions, and columns".
  • Etsuro Fujita sent in two more revisions of a patch to improve the performance of ORDINALITY.
  • Andrew (RhodiumToad) Gierth sent in a WIP patch which implements a method for expanding multiple SRFs in parallel that does not have the surprising LCM behaviour of SRFs-in-select-list. (Functions returning fewer rows are padded with nulls instead.) It then uses this method combined with a parse-time hack to implement the (intended to be) spec-conforming behaviour of UNNEST with multiple parameters, including flattening of composite results.
  • Robert Haas sent in a PoC patch to allow additional "dynamic" memory segments.
  • Etsuro Fujita sent in a patch to update the README in src/backend/optimizer to reflect current realities.
  • Rushabh Lathia sent in two more revisions of a patch to throw an error when years with >4 digits are used in a timestamptz type.
  • Robert Haas sent in a patch to fix a bug where pgstat_reset_remove_files ignores its argument.
  • Michael Cronenworth and Andrew Dunstan traded patches to fix Windows socket error checking for MinGW.
  • Zoltan Boszormenyi sent in another revision of a patch to implement ECPG fetch readahead.
  • Peter Eisentraut sent in a patch to fix an issue with libpq thread locking during SSL connection start.
  • Robert Haas sent in another revision of a patch to rearrange the code for dynamic background workers.
  • Fabrízio de Royes Mello sent in another revision of a patch to add support of "IF NOT EXISTS" to the remaining "CREATE" statements where such a clause would make sense.