Nouvelles hebdomadaires de PostgreSQL - 18 octobre 2009
La Commitfest 2009-09 est maintenant terminée. Vous pouvez recommencer à travailler sur vos propres patchs à présent :)
La "PostgreSQL Conference (JDCon) West" s'est conclue aujourd'hui. Merci à toutes les merveilleuses personnes de Seattle pour en avoir fait un succès.
[ndt] Fin des inscriptions au PGDay.EU 2009 vendredi 23 au soir. Après cette date, ce sera sur place avec une majoration.
[ndt] En bordure du PGDay.EU, David Fetter fera une conférence chez Parinux le 10 novembre. Plus d'infos :
http://www.parinux.org/content/conference-postgresql-le-mardi-11-novembre-2009
Les nouveautés des produits dérivés
(lien vers l'article original)
Offres d'emplois autour de PostgreSQL en octobre
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.
Correctifs appliqués
Tom Lane a commité :
- Move the handling of SELECT FOR UPDATE locking and rechecking out of execMain.c and into a new plan node type LockRows. Like the recent change to put table updating into a ModifyTable plan node, this increases planning flexibility by allowing the operations to occur below the top level of the plan tree. It's necessary in any case to restore the previous behavior of having FOR UPDATE locking occur before ModifyTable does. This partially refactors EvalPlanQual to allow multiple rows-under-test to be inserted into the EPQ machinery before starting an EPQ test query. That isn't sufficient to fix EPQ's general bogosity in the face of plans that return multiple rows per test row, though. Since this patch is mostly about getting some plan node infrastructure in place and not about fixing ten-year-old bugs, I will leave EPQ improvements for another day. Another behavioral change that we could now think about is doing FOR UPDATE before LIMIT, but that too seems like it should be treated as a followon patch.
- Support GRANT/REVOKE ON ALL TABLES/SEQUENCES/FUNCTIONS IN SCHEMA. Petr Jelinek
- Use plurals (TABLES, FUNCTIONS, etc) in ALTER DEFAULT PRIVILEGES. We have the keywords as a consequence of the GRANT ALL patch, so we might as well use them and make the ALTER commands read more naturally.
- Code review for LIKE INCLUDING patch --- clean up some cosmetic and not so cosmetic stuff.
- In pgsql/src/backend/utils/adt/tsvector_op.c, fix ts_stat's failure on empty tsvector. Also insert a couple of Asserts that check for stack overflow. Bogus coding appears to be new in 8.4 --- older releases had a much simpler algorithm here. Per bug #5111.
- Add "\pset linestyle ascii/unicode" option to psql, allowing our traditional ASCII-art style of table output to be upgraded to use Unicode box drawing characters if desired. By default, psql will use the Unicode characters whenever client_encoding is UTF8. The patch forces linestyle=ascii in pg_regress usage, ensuring we don't break the regression tests in Unicode locales. Roger Leigh.
- Support SQL-compliant triggers on columns, ie fire only if certain columns are named in the UPDATE's SET list. Note: the schema of pg_trigger has not actually changed; we've just started to use a column that was there all along. catversion bumped anyway so that this commit is included in the history of potentially interesting changes to system catalog contents. Itagaki Takahiro.
- In pgsql/src/pl/plpython/expected/plpython_unicode_0.out, first committed version of plpython_unicode_0.out did not actually contain the required \200 bytes. Let's see if this commit works, or if CVS is messing it up.
- In pgsql/src/backend/libpq/auth.c, rewrite pam_passwd_conv_proc to be more robust: avoid assuming that the pam_message array contains exactly one PAM_PROMPT_ECHO_OFF message. Instead, deal with however many messages there are, and don't throw error for PAM_ERROR_MSG and PAM_TEXT_INFO messages. This logic is borrowed from openssh 5.2p1, which hopefully has seen more real-world PAM usage than we have. Per bug #5121 from Ryan Douglas, which turned out to be caused by the conv_proc being called with zero messages. Apparently that is normal behavior given the combination of Linux pam_krb5 with MS Active Directory as the domain controller. Patch all the way back, since this code has been essentially untouched since 7.4. (Surprising we've not heard complaints before.)
Andrew Dunstan a commité :
- CREATE LIKE INCLUDING COMMENTS and STORAGE, and INCLUDING ALL shortcut. Itagaki Takahiro.
Alvaro Herrera a commité :
- Add new PGC_S_DATABASE_USER enum value to several places missed by my patch last week. Per note and patch from Jeff Davis.
- Avoid using trivial usernames in foreign_data regression test. Martin Pihlak.
Peter Eisentraut a commité :
- In pgsql/doc/src/sgml/func.sgml, replace unmatched " by " to avoid throwing off syntax highlighters.
- Add alternative expected file for unicode test for client encoding not UTF8.
- In the configure check for the Python distutils module, use a less obscure shell construct to hide away the stderr output. Python 3.1 actually core dumps on the current invocation (
http://bugs.python.org/issue7111), but the new version also has the more general advantage of saving the error message in config.log for analysis.
Heikki Linnakangas a commité :
- In pgsql/src/backend/libpq/auth.c, raise the maximum authentication token (Kerberos ticket) size in GSSAPI and SSPI athentication methods. While the old 2000 byte limit was more than enough for Unix Kerberos implementations, tickets issued by Windows Domain Controllers can be much larger. Ian Turner.
- In pgsql/src/backend/libpq/auth.c, rename the new MAX_AUTH_TOKEN_LENGTH #define to PG_MAX_AUTH_MAX_TOKEN_LENGTH, to make it more obvious that it's a PostgreSQL internal limit, not something that comes from system header files.
- In pgsql/src/bin/scripts/vacuumdb.c, FREEZE and VERBOSE options were in wrong order in the VACUUM command that vacuumdb produces. Per report by Thom Brown.
Michael Meskes a commité :
- Made ECPG more robust against applications freeing strings, based on patch send in by Zoltan Boszormenyi.
Magnus Hagander a commité :
- Write to the Windows eventlog in UTF16, converting the message encoding as necessary. Itagaki Takahiro with some changes from me.
- In pgsql/src/backend/utils/mb/mbutils.c, fix typo in previous release as reported by Itagaki Takahiro, but missed by me.
Correctifs rejetés (à ce jour)
- Pas de déception cette semaine :-)
Correctifs en attente
- Laurenz Albe sent in another revision of the patch to create a hook to test password cryptgraphic strength along with a contrib module to use the hook.
- ITAGAKI Takahiro sent in another revision of the patch to fix encoding issues and eventlog on Win32.
- KaiGai Kohei sent in another revision of the patch for large object ACLs.
- Dave Page sent in a WIP patch to add an application_name GUC which optionally shows the name of the connecting application.
- Peter Eisentraut sent in an updated version of the per-column trigger patch.
- KaiGai Kohei sent in another revision of the ACL rework patch.
- ITAGAKI Takahiro sent in another revision of the per-column trigger patch.
- Zoltan Boszormenyi sent a patch that makes ECPG more robust against applications that free() strings by storing its own copy of the prepared statement name.
- ITAGAKI Takahiro sent in a patch to prevent table rewrites caused by ALTER TABLE from writing WALs.
- Heikki Linnakangas sent in an updated patch for Hot Standby.
- ITAGAKI Takahiro sent in a patch for contrib/auto_explain which adds EXPLAIN (ANALYZE|BUFFERS).
- ITAGAKI Takahiro sent in a WIP patch to add WHEN to triggers.
- Dave Page sent in another revision of the patch to add an application_name GUC and supporting features for same.