PostgreSQL
La base de données la plus sophistiquée au monde.

Ouverture de session

Navigation

Contactez-nous

Administration du site :
"equipe chez postgresqlfr point org"

Contact presse :
"fr chez postgresql point org"

Contact association :
"bureau chez postgresqlfr point org"

Questions PostgreSQL :
 IRC :
  serveur irc.freenode.net
  canal #postgresqlfr

Recherche

Accéder aux archives

« Octobre 2008  
Lun Mar Mer Jeu Ven Sam Dim
  2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31  

Syndication

Flux XML

Sondage

Quelle est la version de PostgreSQL la plus répandue sur vos serveurs ?
8.3
10%
8.2
42%
8.1
40%
8.0
2%
7.4
6%
7.3 ou antérieure
0%
Nombre de votes: 48

Nouvelles neuves de PostgreSQL

PostgreSQL Weekly News | Nouvelles neuves de PostgreSQL

Par N Bougain le 04/01/2008 - 00:27

Nouvelles hebdomadaires de Postgres - 30 décembre 2007

Bonne Année !

Bien qu'étant une semaine "fériée", beaucoup de choses s'y sont produites. Jetez un œil sur la liste des patchs pour les détails.

Les nouveautés des produits dérivés

Offres d'emplois autour de Postgres en décembre

http://archives.postgresql.org/pgsql-jobs/2007-12/threads.php

Postgres Local

  • Les PGCon 2008 auront lieu du 20 au 23 mai à Ottawa - propositions acceptées dès à présent :
    http://www.pgcon.org/2008/papers.php
  • Les équipes BSD et PostgreSQL partageront un espace développeurs au FOSDEM 2008 de Bruxelles (23-24 février). Si vous souhaitez donner une conférence ou aider sur le stand, contactez fosdem (a) pgug (.) eu. Pour plus d'informations, jetez un œil sur :
    http://fosdem.org/2008/schedule/devroom/bsdpostgresql
  • La PostgreSQL Conference East '08 est programmée les 28 et 29 mars 2008 à l'Université du Maryland, College Park :
    http://www.postgresqlconference.org/
  • Le FISL 9.0 se déroulera du 17 au 19 avril 2008 à la PUCRS de Porto Alegre (Brésil). Les propositions de conférences sont attendues avant le 11 janvier :
    https://fisl.softwarelivre.org/9.0/

Postgres dans les média

Postgres Weekly News / les nouvelles hebdomadaires vous sont offertes cette semaine par David Fetter. La traduction française est effectuée par l'équipe PostgreSQLFr.

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

Alvaro Herrera a commité :

  • In pgsql/contrib/uuid-ossp: uuid-ossp.c, add missing return code checks in the uuid-ossp contrib module, per bug #3841.

Andrew Dunstan a commité :

  • In pgsql/src/backend/commands/copy.c, add sanity check to ensure delimiter and quote are different in CSV mode.

Michael Meskes a commité :

  • In ecpg, applied patch send by ITAGAKI Takahiro to fix bug in connect statement if user name is a variable. Also fixed test case that didn't detect this.

Tom Lane a commité :

  • In pgsql/src/backend/commands/copy.c, swap the order of testing for control characters and for column delimiter in CopyAttributeOutText(), so that control characters are converted to the C-style escape sequences even if they happen to be equal to the column delimiter (as is true by default for tab, for example). Oversight in my previous patch to restore pre-8.3 behavior of COPY OUT escaping. Per report from Tomas Szepe.
  • In pgsql/src/backend/commands/copy.c, fix ill-advised usage of x?y:z expressions in errmsg() and errhint() calls. This prevented gettext from recognizing the strings that need to be translated.
  • In pgsql/src/backend/commands/copy.c, disallow digits and lower-case ASCII letters as the delimiter in non-CSV COPY. We need a restriction here because when the delimiter occurs as a data character, it is emitted with a backslash, and that will only work as desired if CopyReadAttributesText() will interpret the backslash sequence as representing the second character literally. This is currently untrue for 'b', 'f', 'n', 'r', 't', 'v', 'x', and octal digits. For future-proofing and simplicity of explanation, it seems best to disallow a-z and 0-9. We must also disallow dot, since "\." by itself would look like copy EOF. Note: "\N" is by default the null print string, so N would also cause a problem, but that is already tested for.
  • Improve consistency of error reporting in GUC assign_hook routines. Some were reporting ERROR for interactive assignments and LOG for other cases, some were saying nothing for non-interactive cases, and a few did yet other things. Make them use a new function GUC_complaint_elevel() to establish a reasonably uniform policy about how to report. There are still a few edge cases such as assign_search_path(), but it's much better than before. Per gripe from Devrim Gunduz and subsequent discussion. As noted by Alvaro, it'd be better to fold these custom messages into the standard "invalid parameter value" complaint from guc.c, perhaps as the DETAIL field. However that will require more redesign than seems prudent for 8.3. This is a relatively safe, low-impact change that we can afford to risk now.
  • Update examples in planstats.sgml for 8.3, and improve some aspects of that discussion. Add a link from perform.sgml.
  • Improve a number of elog messages for not-supposed-to-happen cases in btrees, since these seem to happen after all in corrupted indexes. Make sure we supply the index name in all cases, and provide relevant block numbers where available. Also consistently identify the index name as such. Back-patch to 8.2, in hopes that this might help Mason Hale figure out his problem.

Peter Eisentraut a commité :

  • Wording improvements in pgsql/src/backend/tsearch/ts_utils.c, pgsql/src/backend/utils/adt/tsquery.c, pgsql/src/backend/utils/adt/tsquery_cleanup.c, pgsql/src/backend/utils/adt/tsvector_op.c, pgsql/src/backend/utils/misc/guc.c and pgsql/src/port/open.c.
  • In pgsql/doc/src/sgml/docguide.sgml, update required TeX settings.
  • In pgsql/doc/src/sgml/stylesheet.dsl, disable LOT for the time being because of TeX problems.
  • In pgsql/src/port/open.c, change may to might.

Bruce Momjian a commité :

  • Add documentation section about preventing server spoofing. Update SSL documention to be clearer about certificates, and restructure for clarity.
  • Add two documentation tables to outline SSL file usage for client and server.
  • Update docs to clarify purpose of SSL key file.
  • In pgsql/doc/src/sgml/libpq.sgml, update docs: client always gets server certificate.
  • In pgsql/doc/src/sgml/runtime.sgml, document problem with NULL SSL ciphers and man-in-the-middle attacks.
  • In pgsql/doc/src/sgml/runtime.sgml, improve wording of NULL SSL cipher.
  • In pgsql/doc/src/sgml/client-auth.sgml, update docs mentioning PAM doesn't work reading /etc/passwd because of non-root. Dhanaraj M
  • In pgsql/doc/src/sgml/runtime.sgml, document that null ciphers are not recommended. Mark Mielke
  • In pgsql/doc/src/sgml/runtime.sgml, remove tab in file name.
  • In pgsql/doc/src/sgml/wal.sgml, document how to control the disk write cache on Solaris. Zdenek Kotala
  • Update Japanese FAQ. Jun Kuwamura.
  • Add to TODO: Allow SSL authentication/encryption over unix domain sockets :
    http://archives.postgresql.org/pgsql-hackers/2007-12/msg00924.php
  • Remove TODO.detail for pg_upgrade.
  • Update TODO list based on 8.3 completed items.

Correctifs rejetés (à ce jour)

  • Pas de déception cette semaine :-)

Correctifs en attente

  • Hans-Juergen Schoenig sent in a patch which updates Evgen Potemkin's CONNECT BY PRIOR patch.

© PostgreSQLFr, tous droits rĂ©servĂ©s.
Site déclaré à la CNIL sous le numéro 1074678, conformément à la Loi en vigueur.