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 SAS le 27/02/2007 - 10:54

Nouvelles hebdomadaires de PostgreSQL - 25 février 2007

Le fonds PostgreSQL du SPI a financé ce mois-ci le déplacement de David Fetter à Consili, Brésil, où il a donné une conférence.
Le fonds finance également Neil Conway pour les deux prochains mois qu'il passera à vérifier les correctifs de la version 8.3.

Une discussion animée (Lively Discussion(TM)) se poursuit sur -hackers au sujet de la gestion du code source.

Le septième Framework Programme (FP7) est ouvert aux propositions. Les organisations européenne de PostgreSQL sont encouragées à déposer une proposition :) http://cordis.europa.eu/fp7/home_en.html

search.postgresql.org peut désormais être utilisé comme plugin à la boîte de recherche de firefox. http://www.gunduz.org/postgresql/searchpostgresqlorg.html

Les nouveautés des produits dérivés

Les jobs PostgreSQL Jobs de février

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

PostgreSQL Local

Il y aura un stand PostgreSQL les 3 et 4 mars à Chemnitz, RFA. Quelques personnalités incontournables des communautées PostgreSQL de langue allemande y seront. Contacter info@pgug.de pour en être.
http://chemnitzer.linux-tage.de/2007/info/

La communauté PostgreSQL italienne recherche des mécènes pour la journée PostgreSQL du Prato, Italie, cet été. Suivre le lien pour participer :
http://www.pgday.it

PostgreSQL dans les média


PostgreSQL Weekly News vous est présenté cette semaine par David Fetter, Josh Berkus and Devrim GUNDUZ.
Adaptation francophone de Stéphane Schildknecht.

Vos propositions d'informations doivent parvenir avant dimanche minuit à david@fetter.org.

Correctifs appliqués

Andrew Dunstan a commité :

  • Allow pltcl args to spi_prepare and plpython args to plpy.prepare to be standard type aliases as well as those known in pg_type. Similar to recent change in plperl.

Peter Eisentraut a commité :

  • Bernd Helmle's patch which identifies the schema of inherited tables in psql \d when necessary.
  • Add missing OIDs from xml support to pg_proc, bump catversion.

Bruce Momjian a commité :

  • Move test for BLCKSZ < 1024 to guc.c.
  • Spelling fix in Solaris FAQ.
  • Update Solaris FAQ per Peter Eisentraut.
  • Updated FAQ on upgrading.
  • Zdenek Kotala's patch to the Solaris FAQ.
  • Chad Wagner's patch to psql which adds \prompt capability.
  • Remove extra tab from pgsql/doc/src/sgml/ref/psql-ref.sgml.
  • Remove tabs from SGML reference files so their addition can be detected in the future.
  • Update message wording in FAQ.
  • Update new optional VACUUM FULL hint for translations, per Alvaro Herrera.
  • Simon Riggs's patch which moves increase FSM warning to after lazy_truncate_heap() because the function might reduce the number of free pages in the table. Recommend VACUUM FULL only if 20% free.
  • Heikki Linnakangas's patch to clean up the btree source code.
  • Update FAQ about minor updates.
  • Jun Kuwamura's update to the Japanese FAQ.
  • Update URL in German FAQ for bug form, per Schima, Fabian
  • Daojing Zhou's update of the Chinese FAQs to have two versions, a traditional Chinese version (Taiwan) and a Simplified version (China (PRC)). Backpatch to 8.2.X.
  • Update minor release text in FAQ.
  • Add configure --enable-profiling to enable GCC profiling. Patches from Korry Douglas and Nikhil S
  • Update upgrade text in FAQ.
  • Update URL for set-returning functions in FAQ.
  • Add URL for "Allow row and record variables to be set to NULL constants, and allow NULL tests on such variables" in the TODO list.
  • Prevent BLCKSZ < 1024, and have initdb test shared buffers based on the BLCKSZ value.
  • Add to TODO: "Consider decreasing the amount of memory used by PrivateRefCount."
  • Fix markup in pgsql/doc/src/sgml/information_schema.sgml.
  • Change $(CC) to $(COMPILER) on Solaris gcc so -m64 is passed into the shared link line.
  • Add to TODO: "Increase locking when DROPing objects so dependent objects cannot get dropped while the DROP operation is happening."
  • Add URL for "Allow UPDATE/DELETE WHERE CURRENT OF cursor" in TODO list.
  • Add to TODO: "Add missing operators for geometric data types. Some geometric types do not have the full suite of geometric operators, e.g. box @> point."
  • Update "encode" documentation to mention that 'escape' only changes null bytes and backslashes, remove "ASCII" mention. Backpatch to 8.2.X.
  • Update pgpass Win32 wording.
  • Update information_schema documentation to match system tables. Backpatch to 8.2.X.
  • Improve wording on Julian dates in pgsql/doc/src/sgml/func.sgml.
  • More clearly document that most PostgreSQL utilities support libpq environment variables. Backpatch to 8.2.X.
  • Remove from TODO for Win32: "Check .pgpass file permissions." It is not needed.
  • In pgsql/src/interfaces/libpq/fe-connect.c, add comment that on Win32, we don't need to check the .pgpass file permission, per Magnus Hagander.
  • Add to TODO for Win32: "Check .pgpass file permissions."
  • Update array slice documentation to be clearer.
  • Add to TODO: "Fix IS OF so it matches the ISO specification, and add documentation."
  • Comment-out documentation for IS OF because it doesn't conform to the ISO SQL behavior. Backpatch removal to 8.2.X.
  • Remove TODO item: "ARRAY[[1,2],[3,4]])[1] should return the same values as ARRAY[[1,2],[3,4]])[1:1]." It actually shouldn't.
  • Add text about Makefile.custom to FAQ_DEV.
  • Document that to_char('J'/Julian) is midnight-based, per report that Julian technically is noon to noon.
  • Improve wording in isodow documentation.
  • Update PQfree() documentation to be clearer, backpatch to 8.2.X.
  • Add to TODO: "Allow user configuration of TOAST thresholds."
  • Add newlines to TODO.
  • Add to TODO: "Allow UPDATEs on only non-referential integrity columns not to conflict with referential integrity locks."
  • Add to TODO: "Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause."
  • Clarify documentation that initdb -A or editing pg_hba.conf is required if you do not trust local users.
  • Clarify documentation for "day of the week" handling for to_char() and EXTRACT().
  • Mark TODO as done: "Add ISO day of week format 'ID' to to_char() where Monday = 1."
  • Add "isodow" option to EXTRACT() and date_part() where Sunday = 7.
  • Mark TODO as done: "Add a field 'isoyear' to extract(), based on the ISO week."
  • Mark TODO as done: "Add long file support for binary pg_dump output."

Magnus Hagander a commité :

  • In pgsql/src/tools/msvc/Solution.pm, revert changes to process pg_proc.h entries without OIDs. We're not supposed to have such entries, and want to be notified when we do... Leave the plain bug fix in genbki.
  • Fix pg_dump on Win32 so that it properly dumps files larger than 2GB when using binary dump formats.
  • Parse pg_proc.h with entries without OIDs for the MSVC build.

Tom Lane a commité :

  • Update 7.x variant horology files to match the new US DST rules. It seems likely that anyone wanting to run the regression tests in the future will have up-to-date system timezone files, so this is more likely to work than the old contents.
  • Put back copyObject() call I removed in a fit of brain fade. This one is still needed despite cleanups in setrefs.c, because the point is to let the inserted Result node compute a different tlist than its input node does. Per example from Jeremy Drake.
  • Now that plans have flat rangetable lists, it's a lot easier to get EXPLAIN to drill down into subplan targetlists to print the referent expression for an OUTER or INNER var in an upper plan node. Hence, make it do that always, and banish the old hack of showing "?columnN?" when things got too complicated. Along the way, fix an EXPLAIN bug I introduced by suppressing subqueries from execution-time range tables: get_name_for_var_field() assumed it could look at rte->subquery to find out the real type of a RECORD var. That doesn't work anymore, but instead we can look at the input plan of the SubqueryScan plan node.
  • Change Agg and Group nodes so that Vars contained in their targetlists and quals have varno OUTER, rather than zero, to indicate a reference to an output of their lefttree subplan. This is consistent with the way that every other upper-level node type does it, and allows some simplifications in setrefs.c and EXPLAIN.
  • Fix bug I introduced in recent patch to make hash joins discard null tuples immediately: ExecHashGetHashValue failed to restore the caller's memory context before taking the failure exit.
  • Turn the rangetable used by the executor into a flat list, and avoid storing useless substructure for its RangeTblEntry nodes. (I chose to keep using the same struct node type and just zero out the link fields for unneeded info, rather than making a separate ExecRangeTblEntry type --- it seemed too fragile to have two different rangetable representations.) Along the way, put subplans into a list in the toplevel PlannedStmt node, and have SubPlan nodes refer to them by list index instead of direct pointers. Vadim wanted to do that years ago, but I never understood what he was on about until now. It makes things a *whole* lot more robust, because we can stop worrying about duplicate processing of subplans during expression tree traversals. That's been a constant source of bugs, and it's finally gone. There are some consequent simplifications yet to be made, like not using a separate EState for subplans in the executor, but I'll tackle that later.
  • Adjust user-facing documentation to explain why we don't check pgpass file permissions on Windows.
  • Remove the Query structure from the executor's API. This allows us to stop storing mostly-redundant Query trees in prepared statements, portals, etc. To replace Query, a new node type called PlannedStmt is inserted by the planner at the top of a completed plan tree; this carries just the fields of Query that are still needed at runtime. The statement lists kept in portals etc. now consist of intermixed PlannedStmt and bare utility-statement nodes --- no Query. This incidentally allows us to remove some fields from Query and Plan nodes that shouldn't have been there in the first place. Still to do: simplify the execution-time range table; at the moment the range table passed to the executor still contains Query trees for subqueries. initdb forced due to change of stored rules.
  • Get rid of some old and crufty global variables in the planner. When this code was last gone over, there wasn't really any alternative to globals because we didn't have the PlannerInfo struct being passed all through the planner code. Now that we do, we can restructure things to avoid non-reentrancy. I'm fooling with this because otherwise I'd have had to add another global variable for the planned compact range table list.

Correctifs rejetés (à ce jour)

Mateo Beccati's patch which gets PostgreSQL to compile on Irix 6.5, but the patch would break most Linux machines.

Correctifs en attente

  • Zoltan Boszormenyi sent in two more iterations of his IDENTITY/GENERATED patch.
  • Pavan Deolasee sent in two more versions of his work-in-progress HOT patch.
  • Gregory Stark sent in a patch to shorten varlena headers.
  • Guillaume Smet sent in a first implementation of GIN for pg_trgm.
  • Nikolay Samokhvalov sent in a patch to implement xpath_array with namespaces support.
  • Darcy Buskermolen sent in a patch which provides for logging in the event that -k is unable to clean up an old WAL file and makes the "failed to remove file" error message consistent for the trigger file.
  • Greg Sabino Mullane sent in a documentation patch which warns about some strange behavior in LISTEN/NOTIFY.
  • Pavel Stehule sent in a patch to add timestamp support for XSD-type timestamps.
  • Simon Riggs sent in another version of his patch to avoid deadlocks in pg_dump.
  • Joachim Wieland sent in a patch which makes GUC values fall back to their default values when they got removed (or commented) from the configuration file.
  • Kris Jurka sent in a patch which implements lo_truncate for truncating large objects to a given length. This is required for implementing Blob.truncate in the JDBC driver and rounds out filesystem like functionality for large objects.
  • Simon Riggs sent a bug fix for his recent optimization of COPY-after-truncate.

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