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

Ouverture de session



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 :
  canal #postgresqlfr


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  


Flux XML


Quelle est la version de PostgreSQL la plus répandue sur vos serveurs ?
7.3 ou antérieure
Nombre de votes: 48

Nouvelles neuves de PG

PostgreSQL Weekly News | Nouvelles neuves de PG

Par N Bougain le 12/09/2007 - 00:45

Nouvelles hebdomadaires de PostgreSQL - 9 Septembre 2007

Les nouveautés des produits dérivés

Offres d'emplois autour de PostgreSQL en septembre

PostgreSQL Local

PostgreSQL dans les média

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

Proposez vos articles ou annonces avant dimanche 15:00 (heure du Pacifique). Envoyez-les en anglais à david (a) ou en allemand à pwn (a)

Correctifs appliqués

Teodor Sigaev a commité :

  • Improve page split in rtree emulation. Now when a split result has a big misalignement, it tries to split page basing on distribution of box's centers. Per report from Tom Dolafi.
  • Fix infinite loop in rank_cd for some corner queries. Per Daniele Varrazzo.
  • Improvements from Heikki Linnakangas.
  • Improve various checks by Heikki Linnakangas.
  • Refactor of tsearch code by Heikki Linnakangas with small editorization by me.
  • Add turkish stopword list. Thanks to Devrim GUNDUZ.

Bruce Momjian a commité :

Andrew Dunstan a commité :

  • Fix typo in regression Makefile.
  • Provide for a file specifying non-standard config options for temp install for pg_regress, via --temp-config option. Pick this up in the make file via TEMP_CONFIG setting.
  • Provide for binary input/output of enums, to fix complaint from Merlin Moncure. This just provides text values, we're not exposing the underlying Oid representation. Catalog version bumped.

Michael Meskes a commité :

  • In pgsql/src/interfaces/ecpg, synced parser and keyword list.

Tom Lane a commité :

  • Set the correct context (PGC_SIGHUP) for log_autovacuum, per ITAGAKI Takahiro. Fix grammatical errors in its description.
  • Code review for GUC revert-values-if-removed-from-postgresql.conf patch; and in passing, fix some bogosities dating from the custom_variable_classes patch. Fix guc-file.l to correctly check changes in custom_variable_classes that are attempted concurrently with additions/removals of custom variables, and don't allow the new setting to be applied in advance of checking it. Clean up messy and undocumented situation for string variables with NULL boot_val. Fix DefineCustomVariable functions to initialize boot_val correctly. Prevent find_option from inserting bogus placeholders for custom variables that are simply inquired about rather than being set.
  • Replace the former method of determining snapshot xmax --- to wit, calling ReadNewTransactionId from GetSnapshotData --- with a "latestCompletedXid" variable that is updated during transaction commit or abort. Since latestCompletedXid is written only in places that had to lock ProcArrayLock exclusively anyway, and is read only in places that had to lock ProcArrayLock shared anyway, it adds no new locking requirements to the system despite being cluster-wide. Moreover, removing ReadNewTransactionId from snapshot acquisition eliminates the need to take both XidGenLock and ProcArrayLock at the same time. Since XidGenLock is sometimes held across I/O this can be a significant win. Some preliminary benchmarking suggested that this patch has no effect on average throughput but can significantly improve the worst-case transaction times seen in pgbench. Concept by Florian Pflug, implementation by Tom Lane.
  • Don't take ProcArrayLock while exiting a transaction that has no XID; there is no need for serialization against snapshot-taking because the xact doesn't affect anyone else's snapshot anyway. Per discussion. Also, move various info about the interlocking of transactions and snapshots out of code comments and into a hopefully-more-cohesive discussion in access/transam/README. Also, remove a couple of now-obsolete comments about having to force some WAL to be written to persuade RecordTransactionCommit to do its thing.
  • Allow CREATE INDEX CONCURRENTLY to disregard transactions in other databases, per gripe from hubert depesz lubaczewski. Patch from Simon Riggs.
  • Make eval_const_expressions() preserve typmod when simplifying something like null::char(3) to a simple Const node. (It already worked for non-null values, but not when we skipped evaluation of a strict coercion function.) This prevents loss of typmod knowledge in situations such as exhibited in bug #3598. Unfortunately there seems no good way to fix that bug in 8.1 and 8.2, because they simply don't carry a typmod for a plain Const node. In passing I made all the other callers of makeNullConst supply "real" typmod values too, though I think it probably doesn't matter anywhere else.
  • Volatile-qualify the ProcArray PGPROC pointer in a bunch of routines that examine fields that could change under them. This is just to make really sure that when we are fetching a value 'only once', that's what actually happens. Possibly this is a bug that should be back-patched, but in the absence of solid evidence that it's needed, I won't bother.
  • Quick hack to make the VXID of a prepared transaction be -1/XID, so that different prepared xacts can be told apart in the pg_locks view. Per suggestion from Florian.
  • Implement lazy XID allocation: transactions that do not modify any database rows will normally never obtain an XID at all. We already did things this way for subtransactions, but this patch extends the concept to top-level transactions. In applications where there are lots of short read-only transactions, this should improve performance noticeably; not so much from removal of the actual XID-assignments, as from reduction of overhead that's driven by the rate of XID consumption. We add a concept of a "virtual transaction ID" so that active transactions can be uniquely identified even if they don't have a regular XID. This is a much lighter-weight concept: uniqueness of VXIDs is only guaranteed over the short term, and no on-disk record is made about them. Florian Pflug, with some editorialization by Tom.
  • In pgsql/doc/src/sgml/textsearch.sgml, sync examples of psql \dF output with current CVS HEAD behavior. Random other wordsmithing.
  • Support SET FROM CURRENT in CREATE/ALTER FUNCTION, ALTER DATABASE, ALTER ROLE. (Actually, it works as a plain statement too, but I didn't document that because it seems a bit useless.) Unify VariableResetStmt with VariableSetStmt, and clean up some ancient cruft in the representation of same.

Correctifs rejetés (à ce jour)

  • Pas de déception cette semaine :-)

Correctifs en attente

  • Heikki Linnakangas sent in a document update to version 14 of the HOT patch.
  • Heikki Linnakangas sent in a refactor for the tsearch2 code.
  • Pavan Deolasee sent in version 15 of the HOT patch.
  • Andrew Dunstan sent in a patch which adds temp_config configuration.
  • Greg Smith sent in a patch which does just-in-time background writing.
  • Tom Lane sent in a WIP patch for latestCompletedXid method of computing snapshot xmax.
  • Andrew Dunstan sent in a WIP patch to replace MSVC build scripts build.bat and vcregress.bat with and respectively.
  • Sibte Abbas sent in a patch which implements the \# TODO for psql.

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