Offres d'emplois autour de PostgreSQL en janvier

PostgreSQL Local

  • FOSDEM PGDay, une conférence d'une journée, tenue avant le FOSDEM à Bruxelles, aura lieu le 31 janvier 2014. Détails : http://fosdem2014.pgconf.eu/ http://fosdem2014.pgconf.eu/registration/
  • La 7ème conférence annuelle "Prague PostgreSQL Developers Day" (P2D2), organisée par le CSPUG (PUG tchèque et slovaque), aura lieu le 6 février 2014 à la Faculté des Sciences Mathématiques & Physiques de l'Université Charles (Malostranske namesti 25, Prague). Infos en langue tchèque ci-après : http://www.p2d2.cz/
  • Le PGDay Nordique 2014 aura lieu à Stockholm (Suède) à l'hôtel Hilton le 20 mars 2014. L'appel à conférenciers est ouvert jusqu'au 2 février 2014 : http://2014.nordicpgday.org/
  • La PGConf NYC 2014 aura lieu les 3 & 4 avril 2014 à New-York (New-York, USA) : http://nyc.pgconf.us/2014/
  • Le sommet Open Data aura lieu le 11 avril 2014 à Denver (Colorado, États-Unis) : http://www.opendatasummit.com
  • La PGCon 2014, la conférence mondiale des développeurs PostgreSQL, se tiendra à Ottawa (Ontario, Canada) du 20 au 24 mai 2014 : http://www.pgcon.org/2014/

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é :

Fujii Masao a poussé :

Tom Lane a poussé :

  • Fix to_timestamp/to_date's handling of consecutive spaces in format string. When there are consecutive spaces (or other non-format-code characters) in the format, we should advance over exactly that many characters of input. The previous coding mistakenly did a "skip whitespace" action between such characters, possibly allowing more input to be skipped than the user intended. We only need to skip whitespace just before an actual field. This is really a bug fix, but given the minimal number of field complaints and the risk of breaking applications coded to expect the old behavior, let's not back-patch it. Jeevan Chalke http://git.postgresql.org/pg/commitdiff/9a8f5729b4625ec0468ad5a48296c3e729cf3e65
  • Remove pg_stat_statements--1.1.sql. Commit 91484409bdd17f330d10671d388b72d4ef1451d7 should have removed this file, not just reduced it to zero size. http://git.postgresql.org/pg/commitdiff/fe0c690dfdcf628671d62d04caa39449fdc56078
  • Tweak parse location assignment for CURRENT_DATE and related constructs. All these constructs generate parse trees consisting of a Const and a run-time type coercion (perhaps a FuncExpr or a CoerceViaIO). Modify the raw parse output so that we end up with the original token's location attached to the type coercion node while the Const has location -1; before, it was the other way around. This makes no difference in terms of what exprLocation() will say about the parse tree as a whole, so it should not have any user-visible impact. The point of changing it is that we do not want contrib/pg_stat_statements to treat these constructs as replaceable constants. It will do the right thing if the Const has location -1 rather than a valid location. This is a pretty ugly hack, but then this code is ugly already; we should someday replace this translation with special-purpose parse node(s) that would allow ruleutils.c to reconstruct the original query text. (See also commit 5d3fcc4c2e137417ef470d604fee5e452b22f6a7, which also hacked location assignment rules for the benefit of pg_stat_statements.) Back-patch to 9.2 where pg_stat_statements grew the ability to recognize replaceable constants. Kyotaro Horiguchi http://git.postgresql.org/pg/commitdiff/69c7a9838c82bbfdd61301c697e3774e9543805e
  • Allow use of "z" flag in our printf calls, and use it where appropriate. Since C99, it's been standard for printf and friends to accept a "z" size modifier, meaning "whatever size size_t has". Up to now we've generally dealt with printing size_t values by explicitly casting them to unsigned long and using the "l" modifier; but this is really the wrong thing on platforms where pointers are wider than longs (such as Win64). So let's start using "z" instead. To ensure we can do that on all platforms, teach src/port/snprintf.c to understand "z", and add a configure test to force use of that implementation when the platform's version doesn't handle "z". Having done that, modify a bunch of places that were using the unsigned-long hack to use "z" instead. This patch doesn't pretend to have gotten everyplace that could benefit, but it catches many of them. I made an effort in particular to ensure that all uses of the same error message text were updated together, so as not to increase the number of translatable strings. It's possible that this change will result in format-string warnings from pre-C99 compilers. We might have to reconsider if there are any popular compilers that will warn about this; but let's start by seeing what the buildfarm thinks. Andres Freund, with a little additional work by me http://git.postgresql.org/pg/commitdiff/ac4ef637ad2ff2a24847f67d14027b8745f6741e
  • Code review for auto-tuned effective_cache_size. Fix integer overflow issue noted by Magnus Hagander, as well as a bunch of other infelicities in commit ee1e5662d8d8330726eaef7d3110cb7add24d058 and its unreasonably large number of followups. http://git.postgresql.org/pg/commitdiff/2850896961994aa0993b9e2ed79a209750181b8a

Alvaro Herrera a poussé :

Robert Haas a poussé :

Stephen Frost a poussé :

  • Allow type_func_name_keywords in even more places. A while back, 2c92edad48796119c83d7dbe6c33425d1924626d allowed type_func_name_keywords to be used in more places, including role identifiers. Unfortunately, that commit missed out on cases where name_list was used for lists-of-roles, eg: for DROP ROLE. This resulted in the unfortunate situation that you could CREATE a role with a type_func_name_keywords-allowed identifier, but not DROP it (directly- ALTER could be used to rename it to something which could be DROP'd). This extends allowing type_func_name_keywords to places where role lists can be used. Back-patch to 9.0, as 2c92edad48796119c83d7dbe6c33425d1924626d was. http://git.postgresql.org/pg/commitdiff/6c36f383df728866d7085c155cbe45ebc07b195f
  • ALTER TABLESPACE ... MOVE ... OWNED BY. Add the ability to specify the objects to move by who those objects are owned by (as relowner) and change ALL to mean ALL objects. This makes the command always operate against a well-defined set of objects and not have the objects-to-be-moved based on the role of the user running the command. Per discussion with Simon and Tom. http://git.postgresql.org/pg/commitdiff/fbe19ee3b87590f1006d072be5fecf8a33d4e9f5
  • Avoid minor leak in parallel pg_dump. During parallel pg_dump, a worker process closing the connection caused a minor memory leak (particularly minor as we are likely about to exit anyway). Instead, free the memory in this case prior to returning NULL to indicate connection closed. Spotting by the Coverity scanner. Back patch to 9.3 where this was introduced. http://git.postgresql.org/pg/commitdiff/6794a9f9a194e24862e60a918eac031b7641686c
  • Use E, not e, for escaping in example docs. From the Department of Nitpicking, be consistent with other escaping and use 'E' instead of 'e' to escape the string in the example docs for GET DISAGNOSTICS stack = PG_CONTEXT. Noticed by Department Chief Magnus Hagander. http://git.postgresql.org/pg/commitdiff/00ba97365d356823c48c02147b4cd66f8f06b1d6
  • Check dup2() results in syslogger. Consistently check the dup2() call results throughout syslogger.c. It's pretty unlikely that they'll error out, but if they do, ereport(FATAL) instead of blissfully continuing on. Spotted by the Coverity scanner. http://git.postgresql.org/pg/commitdiff/790eaa699e4a9626d8a610ec5844e1fd70d73b4e
  • Fix minor leak in pg_dump. Move allocation to after we check the remote server version, to avoid a possible, very minor, memory leak. This makes us more consistent throughout as most places in pg_dump are done in the same way (due, in part, to previous fixes like this). Spotted by the Coverity scanner. http://git.postgresql.org/pg/commitdiff/152d24f5ddbc535bb437b57856fa3c7c5c630472

Andrew Dunstan a poussé :

Heikki Linnakangas a poussé :

Bruce Momjian a poussé :

Noah Misch a poussé :

Magnus Hagander a poussé :

Correctifs rejetés (à ce jour)

  • No one was disappointed this week

Correctifs en attente

  • Rushabh Lathia sent in two revisions of a patch to improve the operation of NOT NULL constraints on foreign tables.
  • MauMau sent in another revision of a patch to prevent localizing messages in startup.
  • Oskari Saarenmaa sent in another revision of a patch to throttle pg_basebackup's progress report down to a maximum of once per second.
  • KaiGai Kohei sent in another revision of a patch to implement cache_scan as a contrib module atop the custom scan patch.
  • Laurence Rowe sent in two revisions of a patch to implement json_array_elements_text.
  • Jov sent in a patch to ensure that ALTER USER is actually identical to ALTER ROLE.
  • Alvaro Herrera sent in a patch to implement a multixact_freeze_table_age GUC and set its default.
  • Antonin Houska sent in another revision of a patch to allow throttling backups.
  • Jov sent in another revision of a patch to clarify the -F option in psql.
  • Alexander Korotkov and Marti Raudsepp traded patches to implement partial sorting.
  • Michael Paquier sent in another revision of a patch to implement REINDEX CONCURRENTLY.
  • Steve Crawford sent in a patch to document the broad range of inputs to_date() and to_timestamp() accept.
  • Fujii Masao sent in another revision of a patch to fix a bug where disk space in pg_xlog increases during archive recovery.
  • Mitsumasa KONDO sent in two more revisions of a patch to add min and max execute statement time to the pg_stat_statement view.
  • David Rowley and Florian Pflug traded patches to implement negative transition functions for aggregates.
  • Jon Nelson sent in a PoC patch to elide tuples during an external sort.
  • Kyotaro HORIGUCHI sent in another revision of a patch to add trigger information to auto_explain.
  • Christian Kruse sent in four more revisions of a patch to show process IDs of processes holding a lock.
  • Andrew Dunstan sent in two more revisions of a patch to implement more json functions.
  • Andres Freund sent in two more flocks of patches in service of logical changeset extraction.
  • Michael Paquier and Fujii Masao traded patches to implement the pg_stat_archiver view.
  • Dean Rasheed sent in another revision of a patch to implement updatable security barrier views.
  • Ronan Dunklau sent in another revision of a patch to implement triggers on foreign tables.
  • Emre Hasegeli sent in another revision of a patch to add GiST support for inet datatypes.
  • Andres Freund sent in a patch to add %z support to elog() and ereport().
  • MauMau sent in two more revisions of a patch to fix a bug on Windows where pg_ctl always uses the same event source.
  • Craig Ringer sent in another flock of patches in service of implementing row-level access control.
  • Bruce Momjian and Tom Lane traded patches to fix some issues with authentication error messages.
  • Heikki Linnakangas sent in four more revisions of a patch to add a "fast scan" method to GIN indexes.
  • Simon Riggs sent in another revision of a patch to fix a locking issue in ALTER TABLE.
  • Pavel Raiskup sent in another revision of a patch to make locale comparisons more tolerant of fuzz in pg_upgrade.
  • Bruce Momjian sent in a patch to fix some behaviors after VACUUM FULL.
  • MauMau sent in a patch to allow recovery up to a backup point.
  • MauMau sent in another revision of a patch to fix an issue caused by Address Space Layout Randomization in Windows 8/2012.
  • Bruce Momjian sent in a patch to change a test for attnum to an Assert.
  • Marco Atzeri sent in another revision of a patch to make building on Cygwin work better.
  • Pavel Stehule sent in three more revisions of a patch to add an --if-exists option to pg_dump.
  • Bruce Momjian sent in a patch to fix an issue with how INTERVAL handles overflow conditions.
  • Tom Lane sent in a patch to store pg_stat_statements externally.
  • Andrew Dunstan sent in another revision of a patch to implement nested hstore and jsonb atop that.
  • Andrew Dunstan sent in a patch to allow running "make check" with only specified tests.