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 PG

PostgreSQL Weekly News | Nouvelles neuves de PG

Par Jean-Christophe Arnu le 02/07/2007 - 17:55

Nouvelles hebdomadaires de PostgreSQL du 1er Juillet 2007

  • Le PgDay.it a dĂ©butĂ© cette semaine. Il comprend des prĂ©sentations assurĂ©es par Josh Berkus, Federico Campoli, Paolo Cavallini, David Fetter et Enrico Pirozzi.

Nouvelles des produits dérivés

Action locales autour de PostgreSQL

PostgreSQL dans la presse


PostgreSQL Weekly News (en langue anglaise) est Ă©crit cette semaine par David Fetter

Attention : pour apparaitre dans les prochains numĂ©ros de PostgreSQL Weekly news, assurez vous d'avoir envoyĂ© vos informations Ă  David Fetter avant dimanche Ă  15:00, fuseau Pacifique (Pacific Time).

Corrections appliquées

Bruce Momjian a committé:

  • Mark TODO as done: "Reduce checkpoint performance degredation by forcing data to disk."

Neil Conway a commitĂ© :

  • A patch which makes \df+ tell whether a function is IMMUTABLE, STABLE or VOLATILE.

Tom Lane a commitĂ© :

  • Reduce the maximum sleep interval in the autovac launcher to 1 second, so that it responds to SIGQUIT reasonably promptly even on machines where SA_RESTART signals restart a sleep from scratch. (This whole area could stand some rethinking, but for now make it work like the other processes do.) Also some marginal stylistic cleanups.
  • Treat the autovac launcher more like a regular backend, in that we wait for it to die before telling the bgwriter to initiate shutdown checkpoint. Since it's connected to shared memory, this seems more prudent than the alternative of letting it quit asynchronously. Resolves my complaint of yesterday about repeated shutdown checkpoints in CVS HEAD.
  • Avoid memory leakage when a series of subtransactions invoke AFTER triggers that are fired at end-of-statement (as is the normal case for foreign keys, for example). In this situation the per-subxact deferred trigger context is always empty when subtransaction exit is reached; so we could free it, but were not doing so, leading to an intratransaction leak of 8K or more per subtransaction. Per off-list example from Viatcheslav Kalinin subsequent to bug #3418 (his original bug report omitted a foreign key constraint needed to cause this leak). Back-patch to 8.2; prior versions were not using per-subxact contexts for deferred triggers, so did not have this leak.
  • In pgsql/src/backend/storage/ipc/procarray.c, fix comments not updated in recent patch.
  • In pgsql/src/backend/postmaster/autovacuum.c, add 'volatile' to suppress 'variable might be clobbered by longjmp' warning emitted by some versions of gcc.
  • Improve logging of checkpoints. Patch by Greg Smith, worked over by Heikki Linnakangas and a little bit by me.
  • Fix computation of PG_VERSION_NUM by configure: remove unnecessary and unportable backslashes in awk script (per Patrick Welche), and add brackets to prevent autoconf from mangling sed's regexp (the sed call here never did what was expected).
  • In pgsql/doc/src/sgml/backup.sgml, add a note that pg_start_backup will take awhile because of new distributed checkpoint behavior. Explain how to work around this by issuing a manual CHECKPOINT command. Per discussion with Heikki Linnakangas.
  • Fix a passel of ancient bugs in to_char(), including two distinct buffer overruns (neither of which seem likely to be exploitable as security holes, fortunately, since the provoker can't control the data written). One of these is due to choosing to stomp on the output of a called function, which is bad news in any case; make it treat the called functions' results as read-only. Avoid some unnecessary palloc/pfree traffic too; it's not really helpful to free small temporary objects, and again this is presuming more than it ought to about the nature of the results of called functions. Per report from Patrick Welche and additional code-reading by Imad.
  • Fix incorrect tests for undef Perl values in some places in plperl.c. The correct test for defined-ness is SvOK(sv), not anything involving SvTYPE. Per bug #3415 from Matt Taylor. Back-patch as far as 8.0; no apparent problem in 7.x.
  • Implement "distributed" checkpoints in which the checkpoint I/O is spread over a fairly long period of time, rather than being spat out in a burst. This happens only for background checkpoints carried out by the bgwriter; other cases, such as a shutdown checkpoint, are
    still done at full speed. Remove the "all buffers" scan in the bgwriter, and associated stats infrastructure, since this seems no longer very useful when the checkpoint itself is properly throttled. Original patch by Itagaki Takahiro, reworked by Heikki Linnakangas,
    and some minor API editorialization by me.

  • Fix PGXS conventions so that extensions can be built against Postgres installations whose pg_config program does not appear first in the PATH. Per gripe from Eddie Stanley and subsequent
    discussions with Fabien Coelho and others.

Magnus Hagander a commitĂ© :

  • Add notes about configuring Visual Studio Express for use with the Platform SDK.
  • Andrew Dunstan's patch which adds extra checks for buildfarm to pick up errors when running on XP or earlier versions of Windows.

Alvaro Herrera a commitĂ© :

  • Avoid crash in interrupted autovacuum worker, caused by leaving the current memory context pointing at a context not long lived enough. Also, create a fake PortalContext where to store the vac_context, if only to avoid having it be a top-level memory context.
  • Arrange for SIGINT in autovacuum workers to cancel the current table and continue with the schedule. Change current uses of SIGINT to abort a worker into SIGTERM, which keeps the old behaviour of terminating the process. Patch from ITAGAKI Takahiro, with some editorializing of my own.
  • Remove unused "caller" argument from stringToQualifiedNameList.
  • Remove unused BAD_LOCATION definition.
  • Improve autovacuum launcher's ability to detect a problem in worker startup, by having the postmaster signal it when certain failures occur. This requires the postmaster setting a flag in shared memory, but should be as safe as the pmsignal.c code is. Also make sure the launcher honor's a postgresql.conf change turning it off on SIGHUP.

Correctifs rejetés(pour l'instant)

  • Alvaro Herrera's patch to remove SIBackendInit?'s return value.

Correctifs en attente

  • Zdenek Kotala sent in a patch reflecting New Zealand's new DST rules.
  • Gregory Stark sent in a patch to create reserved words for OLAP windowing functions.
  • ITAGAKI Takahiro sent in a bug fix for pgstat_drop_relation.
  • Pavan Deolasee sent in another version of his HOT patch.
  • Dave Page sent in a patch which fixes some bugs in pg_ctl on Windows.
  • Jacob Rief sent in a patch to make SPI-header-files safe for C++ compilers.
  • Patrick Welche sent in a patch intended to address some issues with using XML on OpenBSD.
  • Andrew Dunstan sent in two revisions of a patch intended to allow logging to CSV files.
  • Heikki Linnakangas sent in a document update for pg_start_backup, notifying people that it may now take longer to finish.
  • Kevin Grittner sent in two revisions of a document patch intended to clarify how warm standby works.
  • Robert Treat sent in a patch to improve dblink's connection security.
  • David Fetter sent in a two revisions of a patch which implements ALTER [VIEW | SEQUENCE] RENAME TO.

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