[Trad] [svn:pgfr] r1059 - in traduc/trunk/postgresql: . ref
svncommit at kryskool.org
svncommit at kryskool.org
Ven 6 Juin 15:51:31 CEST 2008
Auteur: gleu
Date: 2008-06-06 15:51:27 +0200 (ven, 06 jun 2008)
Nouvelle Révision: 1059
Modification:
traduc/trunk/postgresql/acronyms.xml
traduc/trunk/postgresql/cvs.xml
traduc/trunk/postgresql/installation.xml
traduc/trunk/postgresql/pgstandby.xml
traduc/trunk/postgresql/ref/create_type.xml
traduc/trunk/postgresql/ref/grant.xml
traduc/trunk/postgresql/release.xml
traduc/trunk/postgresql/version.xml
traduc/trunk/postgresql/xml2.xml
Log:
Mise à jour version 8.3.2.
Modified: traduc/trunk/postgresql/acronyms.xml
===================================================================
--- traduc/trunk/postgresql/acronyms.xml 2008-06-06 13:20:04 UTC (rev 1058)
+++ traduc/trunk/postgresql/acronyms.xml 2008-06-06 13:51:27 UTC (rev 1059)
@@ -321,7 +321,7 @@
<listitem>
<para>
<ulink
- url="http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/README.HOT">Heap-Only
+ url="http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/README.HOT">Heap-Only
Tuples</ulink>, tuples en mémoire seule
</para>
</listitem>
Modified: traduc/trunk/postgresql/cvs.xml
===================================================================
--- traduc/trunk/postgresql/cvs.xml 2008-06-06 13:20:04 UTC (rev 1058)
+++ traduc/trunk/postgresql/cvs.xml 2008-06-06 13:51:27 UTC (rev 1059)
@@ -43,9 +43,8 @@
code source du serveur <productname>PostgreSQL</productname> vers une
machine locale.
La <ulink
- url="http://developer.postgresql.org/index.php/Working_with_CVS">page wiki
- concernant CVS</ulink>, comprend des informations supplémentaires sur le travail
- avec CVS.
+ url="http://wiki.postgresql.org/index.php/Working_with_CVS">page wiki</ulink>
+ comprend des informations supplémentaires sur le travail avec CVS.
</para>
<sect1 id="anoncvs">
@@ -304,7 +303,7 @@
<para>
Le dépôt CVS peut être récupéré à l'aide de la commande :
<programlisting>
-rsync -avzCH --delete anoncvs.postgresql.org::pgsql-cvs cvsroot/
+rsync -avzH --delete anoncvs.postgresql.org::pgsql-cvs cvsroot/
</programlisting>
Pour des instructions complètes, lire la section « rsync » dans
les
Modified: traduc/trunk/postgresql/installation.xml
===================================================================
--- traduc/trunk/postgresql/installation.xml 2008-06-06 13:20:04 UTC (rev 1058)
+++ traduc/trunk/postgresql/installation.xml 2008-06-06 13:51:27 UTC (rev 1059)
@@ -355,7 +355,8 @@
<step>
<para>
Dans le cas de la réalisation d'une sauvegarde, assurez-vous que votre
- base de données est en cours de mise à jour. Ceci n'affecte pas l'intégrité
+ base de données n'est pas en pleine mise à jour. Ceci n'affecte pas
+ l'intégrité
de la sauvegarde mais les données modifiées seraient bien sûr non inclus.
Si nécessaire, éditez les droits dans le fichier
<filename>/usr/local/pgsql/data/pg_hba.conf</filename> (ou son équivalent)
Modified: traduc/trunk/postgresql/pgstandby.xml
===================================================================
--- traduc/trunk/postgresql/pgstandby.xml 2008-06-06 13:20:04 UTC (rev 1058)
+++ traduc/trunk/postgresql/pgstandby.xml 2008-06-06 13:51:27 UTC (rev 1059)
@@ -347,7 +347,7 @@
<title>Auteur</title>
<para>
- Simon Riggs
+ Simon Riggs <email>simon at 2ndquadrant.com</email>
</para>
</sect2>
Modified: traduc/trunk/postgresql/ref/create_type.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_type.xml 2008-06-06 13:20:04 UTC (rev 1058)
+++ traduc/trunk/postgresql/ref/create_type.xml 2008-06-06 13:51:27 UTC (rev 1059)
@@ -206,7 +206,7 @@
modifieurs de type seront rejetés si le type n'a pas de
<replaceable class="parameter">type_modifier_input_function</replaceable>.
<replaceable class="parameter">type_modifier_output_function</replaceable>
- convertit la valeur typmod interne en une forme correcte pour l'affichage.
+ convertit la valeur typmod integer en une forme correcte pour l'affichage.
Il doit renvoyer une valeur de type <type>cstring</type> qui est la chaîne
exacte à ajouter au nom du type ; par exemple la fonction de
<type>numeric</type> pourrait renvoyer <literal>(30,2)</literal>. Il est
@@ -438,7 +438,7 @@
<term><replaceable class="parameter">type_modifier_input_function</replaceable></term>
<listitem>
<para>
- Le nom d'une fonction qui convertit les modifieurs numériques pour le
+ Le nom d'une fonction qui convertit un tableau de modifieurs pour le
type vers sa forme interne.
</para>
</listitem>
Modified: traduc/trunk/postgresql/ref/grant.xml
===================================================================
--- traduc/trunk/postgresql/ref/grant.xml 2008-06-06 13:20:04 UTC (rev 1058)
+++ traduc/trunk/postgresql/ref/grant.xml 2008-06-06 13:51:27 UTC (rev 1059)
@@ -136,8 +136,12 @@
<para>
Autorise <xref linkend="sql-select" endterm="sql-select-title"/> sur
toutes les colonnes de la table, vue ou séquence indiquée. Autorise
- aussi l'utilisation de <xref linkend="sql-copy" endterm="sql-copy-title"/>
- TO. Pour les séquences, ce droit autorise aussi l'utilisation de la
+ aussi l'utilisation de <xref linkend="sql-copy" endterm="sql-copy-title">
+ TO.
+ Ce droit est aussi nécessaire pour référencer des valeurs de colonnes
+ existantes avec <xref linkend="sql-update" endterm="sql-update-title"/>
+ ou <xref linkend="sql-delete" endterm="sql-delete-title"/>.
+ Pour les séquences, ce droit autorise aussi l'utilisation de la
fonction <function>currval</function>.
</para>
</listitem>
@@ -159,9 +163,13 @@
<listitem>
<para>
Autorise <xref linkend="sql-update" endterm="sql-update-title"/> sur toute
- colonne de la table indiquée. <literal>SELECT ... FOR UPDATE</literal>
- et <literal>SELECT ... FOR SHARE</literal>
- requièrent également ce droit (en plus du droit <literal>SELECT</literal>).
+ colonne de la table spécifiée. (En fait, toute commande
+ <command>UPDATE</command> non triviale nécessite aussi le droit
+ <literal>SELECT</literal> car elle doit référencer les colonnes pour
+ déterminer les lignes à mettre à jour et/ou calculer les nouvelles
+ valeurs des colonnes.) <literal>SELECT ... FOR UPDATE</literal>
+ et <literal>SELECT ... FOR SHARE</literal> requièrent également ce droit
+ en plus du droit <literal>SELECT</literal>.
Pour les séquences, ce droit autorise l'utilisation des fonctions
<function>nextval</function> et <function>setval</function>.
</para>
@@ -173,7 +181,10 @@
<listitem>
<para>
Autorise <xref linkend="sql-delete" endterm="sql-delete-title"/> d'une
- ligne sur la table indiquée.
+ ligne sur la table indiquée. (En fait, toute commande
+ <command>DELETE</command> non triviale nécessite aussi le droit
+ <literal>SELECT</literal> car elle doit référencer les colonnes pour
+ déterminer les lignes à supprimer.)
</para>
</listitem>
</varlistentry>
@@ -236,7 +247,7 @@
<listitem>
<para>
Autorise la création de tables temporaires lors de l'utilisation
- de la base de données.
+ de la base de données spécifiée.
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/release.xml
===================================================================
--- traduc/trunk/postgresql/release.xml 2008-06-06 13:20:04 UTC (rev 1058)
+++ traduc/trunk/postgresql/release.xml 2008-06-06 13:51:27 UTC (rev 1059)
@@ -67,6 +67,371 @@
review, so each item is truly a community effort.
</para>
+ <sect1 id="release-8-3-2">
+ <title>Release 8.3.2</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2008-06-09</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.3.1.
+ For information about new features in the 8.3 major release, see
+ <xref linkend="release-8-3"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 8.3.2</title>
+
+ <para>
+ A dump/restore is not required for those running 8.3.X.
+ However, if you are upgrading from a version earlier than 8.3.1,
+ see the release notes for 8.3.1.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix <literal>ERRORDATA_STACK_SIZE exceeded</literal> crash that
+ occurred on Windows when using UTF-8 database encoding and a different
+ client encoding (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect archive truncation point calculation for the
+ <literal>%r</literal> macro in <varname>recovery_command</varname> parameters
+ (Simon)
+ </para>
+
+ <para>
+ This could lead to data loss if a warm-standby script relied on
+ <literal>%r</literal> to decide when to throw away WAL segment files.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>ALTER TABLE ADD COLUMN ... PRIMARY KEY</command> so that the new
+ column is correctly checked to see if it's been initialized to all
+ non-nulls (Brendan Jurd)
+ </para>
+
+ <para>
+ Previous versions neglected to check this requirement at all.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>REASSIGN OWNED</command> so that it works on procedural
+ languages too (Alvaro)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix problems with <command>SELECT FOR UPDATE/SHARE</command> occurring as a
+ subquery in a query with a non-<command>SELECT</command> top-level operation
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible <command>CREATE TABLE</command> failure when inheriting the
+ <quote>same</quote> constraint from multiple parent relations that
+ inherited that constraint from a common ancestor (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <function>pg_get_ruledef()</function> to show the alias, if any, attached
+ to the target table of an <command>UPDATE</command> or <command>DELETE</command>
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Restore the pre-8.3 behavior that an out-of-range block number in a
+ TID being used in a TidScan plan results in silently not matching any
+ rows (Tom)
+ </para>
+
+ <para>
+ 8.3.0 and 8.3.1 threw an error instead.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix GIN bug that could result in a <literal>too many LWLocks
+ taken</literal> failure (Teodor)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix broken GiST comparison function for <type>tsquery</type> (Teodor)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <function>tsvector_update_trigger()</function> and <function>ts_stat()</function>
+ to accept domains over the types they expect to work with (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix failure to support enum data types as foreign keys (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid possible crash when decompressing corrupted data
+ (Zdenek Kotala)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix race conditions between delayed unlinks and <command>DROP
+ DATABASE</command> (Heikki)
+ </para>
+
+ <para>
+ In the worst case this could result in deleting a newly created table
+ in a new database that happened to get the same OID as the
+ recently-dropped one; but of course that is an extremely
+ low-probability scenario.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Repair two places where SIGTERM exit of a backend could leave corrupted
+ state in shared memory (Tom)
+ </para>
+
+ <para>
+ Neither case is very important if SIGTERM is used to shut down the
+ whole database cluster together, but there was a problem if someone
+ tried to SIGTERM individual backends.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crash due to incorrect plan generated for an
+ <literal><replaceable>x</replaceable> IN (SELECT <replaceable>y</replaceable>
+ FROM ...)</literal> clause when <replaceable>x</replaceable> and <replaceable>y</replaceable>
+ have different data types; and make sure the behavior is semantically
+ correct when the conversion from <replaceable>y</replaceable>'s type to
+ <replaceable>x</replaceable>'s type is lossy (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix oversight that prevented the planner from substituting known Param
+ values as if they were constants (Tom)
+ </para>
+
+ <para>
+ This mistake partially disabled optimization of unnamed
+ extended-Query statements in 8.3.0 and 8.3.1: in particular the
+ LIKE-to-indexscan optimization would never be applied if the LIKE
+ pattern was passed as a parameter, and constraint exclusion
+ depending on a parameter value didn't work either.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner failure when an indexable <function>MIN</function> or
+ <function>MAX</function> aggregate is used with <literal>DISTINCT</literal> or
+ <literal>ORDER BY</literal> (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner to ensure it never uses a <quote>physical tlist</quote> for a
+ plan node that is feeding a Sort node (Tom)
+ </para>
+
+ <para>
+ This led to the sort having to push around more data than it really
+ needed to, since unused column values were included in the sorted
+ data.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid unnecessary copying of query strings (Tom)
+ </para>
+
+ <para>
+ This fixes a performance problem introduced in 8.3.0 when a very large
+ number of commands are submitted as a single query string.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <function>TransactionIdIsCurrentTransactionId()</function> use binary
+ search instead of linear search when checking child-transaction XIDs
+ (Heikki)
+ </para>
+
+ <para>
+ This fixes some cases in which 8.3.0 was significantly
+ slower than earlier releases.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix conversions between ISO-8859-5 and other encodings to handle
+ Cyrillic <quote>Yo</quote> characters (<literal>e</literal> and <literal>E</literal> with
+ two dots) (Sergey Burladyan)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix several datatype input functions, notably <function>array_in()</function>,
+ that were allowing unused bytes in their results to contain
+ uninitialized, unpredictable values (Tom)
+ </para>
+
+ <para>
+ This could lead to failures in which two apparently identical literal
+ values were not seen as equal, resulting in the parser complaining
+ about unmatched <literal>ORDER BY</literal> and <literal>DISTINCT</literal>
+ expressions.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix a corner case in regular-expression substring matching
+ (<literal>substring(<replaceable>string</replaceable> from
+ <replaceable>pattern</replaceable>)</literal>) (Tom)
+ </para>
+
+ <para>
+ The problem occurs when there is a match to the pattern overall but
+ the user has specified a parenthesized subexpression and that
+ subexpression hasn't got a match. An example is
+ <literal>substring('foo' from 'foo(bar)?')</literal>.
+ This should return NULL, since <literal>(bar)</literal> isn't matched, but
+ it was mistakenly returning the whole-pattern match instead (ie,
+ <literal>foo</literal>).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent cancellation of an auto-vacuum that was launched to prevent
+ XID wraparound (Alvaro)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve <command>ANALYZE</command>'s handling of in-doubt tuples (those
+ inserted or deleted by a not-yet-committed transaction) so that the
+ counts it reports to the stats collector are more likely to be correct
+ (Pavan Deolasee)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>initdb</application> to reject a relative path for its
+ <literal>--xlogdir</literal> (<literal>-X</literal>) option (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <application>psql</application> print tab characters as an appropriate
+ number of spaces, rather than <literal>\x09</literal> as was done in
+ 8.3.0 and 8.3.1 (Bruce)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2008c (for
+ DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba, and
+ Argentina/San_Luis)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add <function>ECPGget_PGconn()</function> function to
+ <application>ecpglib</application> (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect result from <application>ecpg</application>'s
+ <function>PGTYPEStimestamp_sub()</function> function (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix handling of continuation line markers in <application>ecpg</application>
+ (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crashes in <filename>contrib/cube</filename> functions (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix core dump in <filename>contrib/xml2</filename>'s
+ <function>xpath_table()</function> function when the input query returns a
+ NULL value (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <filename>contrib/xml2</filename>'s makefile to not override
+ <literal>CFLAGS</literal>, and make it auto-configure properly for
+ <application>libxslt</application> present or not (Tom)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-3-1">
<title>Release 8.3.1</title>
@@ -77,6 +442,8 @@
<para>
This release contains a variety of fixes from 8.3.0.
+ However, if you are upgrading from a version earlier than 8.3.1,
+ see the release notes for 8.3.1.
</para>
<sect2>
@@ -2984,6 +3351,201 @@
</sect2>
</sect1>
+ <sect1 id="release-8-2-8">
+ <title>Release 8.2.8</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2008-06-09</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.2.7.
+ For information about new features in the 8.2 major release, see
+ <xref linkend="release-8-2"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 8.2.8</title>
+
+ <para>
+ A dump/restore is not required for those running 8.2.X.
+ However, if you are upgrading from a version earlier than 8.2.7,
+ see the release notes for 8.2.7.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix <literal>ERRORDATA_STACK_SIZE exceeded</literal> crash that
+ occurred on Windows when using UTF-8 database encoding and a different
+ client encoding (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>ALTER TABLE ADD COLUMN ... PRIMARY KEY</command> so that the new
+ column is correctly checked to see if it's been initialized to all
+ non-nulls (Brendan Jurd)
+ </para>
+
+ <para>
+ Previous versions neglected to check this requirement at all.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible <command>CREATE TABLE</command> failure when inheriting the
+ <quote>same</quote> constraint from multiple parent relations that
+ inherited that constraint from a common ancestor (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <function>pg_get_ruledef()</function> to show the alias, if any, attached
+ to the target table of an <command>UPDATE</command> or <command>DELETE</command>
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix GIN bug that could result in a <literal>too many LWLocks
+ taken</literal> failure (Teodor)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid possible crash when decompressing corrupted data
+ (Zdenek Kotala)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Repair two places where SIGTERM exit of a backend could leave corrupted
+ state in shared memory (Tom)
+ </para>
+
+ <para>
+ Neither case is very important if SIGTERM is used to shut down the
+ whole database cluster together, but there was a problem if someone
+ tried to SIGTERM individual backends.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix conversions between ISO-8859-5 and other encodings to handle
+ Cyrillic <quote>Yo</quote> characters (<literal>e</literal> and <literal>E</literal> with
+ two dots) (Sergey Burladyan)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix several datatype input functions, notably <function>array_in()</function>,
+ that were allowing unused bytes in their results to contain
+ uninitialized, unpredictable values (Tom)
+ </para>
+
+ <para>
+ This could lead to failures in which two apparently identical literal
+ values were not seen as equal, resulting in the parser complaining
+ about unmatched <literal>ORDER BY</literal> and <literal>DISTINCT</literal>
+ expressions.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix a corner case in regular-expression substring matching
+ (<literal>substring(<replaceable>string</replaceable> from
+ <replaceable>pattern</replaceable>)</literal>) (Tom)
+ </para>
+
+ <para>
+ The problem occurs when there is a match to the pattern overall but
+ the user has specified a parenthesized subexpression and that
+ subexpression hasn't got a match. An example is
+ <literal>substring('foo' from 'foo(bar)?')</literalv>.
+ This should return NULL, since <literal>(bar)</literal> isn't matched, but
+ it was mistakenly returning the whole-pattern match instead (ie,
+ <literal>foo</literal>).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2008c (for
+ DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba, and
+ Argentina/San_Luis)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect result from <application>ecpg</application>'s
+ <function>PGTYPEStimestamp_sub()</function> function (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix broken GiST comparison function for <filename>contrib/tsearch2</filename>'s
+ <type>tsquery</type> type (Teodor)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crashes in <filename>contrib/cube</filename> functions (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix core dump in <filename>contrib/xml2</filename>'s
+ <function>xpath_table()</function> function when the input query returns a
+ NULL value (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <filename>contrib/xml2</filename>'s makefile to not override
+ <literal>CFLAGS</literal> (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <literal>DatumGetBool</literal> macro to not fail with <application>gcc</application>
+ 4.3 (Tom)
+ </para>
+
+ <para>
+ This problem affects <quote>old style</quote> (V0) C functions that
+ return boolean. The fix is already in 8.3, but the need to
+ back-patch it was not realized at the time.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-2-7">
<title>Release 8.2.7</title>
@@ -2994,6 +3556,8 @@
<para>
This release contains a variety of fixes from 8.2.6.
+ For information about new features in the 8.2 major release, see
+ <xref linkend="release-8-2"/>.
</para>
<sect2>
@@ -3262,6 +3826,8 @@
<para>
Cette version contient divers correctifs de la version 8.2.5,
et inclut des corrections pour des failles de sécurité importantes.
+ For information about new features in the 8.2 major release, see
+ <xref linkend="release-8-2"/>.
</para>
<sect2>
@@ -3580,6 +4146,8 @@
<para>
Cette version contient divers correctifs de la version 8.2.4.
+ For information about new features in the 8.2 major release, see
+ <xref linkend="release-8-2"/>.
</para>
<sect2>
@@ -3767,6 +4335,8 @@
<para>
Cette version contient quelques corrections de la 8.2.3, dont la
correction d'une faille de sécurité.
+ For information about new features in the 8.2 major release, see
+ <xref linkend="release-8-2"/>.
</para>
<sect2>
@@ -3918,6 +4488,8 @@
<para>
Cette version contient deux corrections de la 8.2.2.
+ For information about new features in the 8.2 major release, see
+ <xref linkend="release-8-2"/>.
</para>
<sect2>
@@ -3965,6 +4537,8 @@
<para>
Cette version contient quelques corrections de la 8.2.1, dont la
correction d'une faille de sécurité.
+ For information about new features in the 8.2 major release, see
+ <xref linkend="release-8-2"/>.
</para>
<sect2>
@@ -4128,6 +4702,8 @@
<para>
Cette version contient quelques corrections de la 8.2.
+ For information about new features in the 8.2 major release, see
+ <xref linkend="release-8-2"/>.
</para>
<sect2>
@@ -6834,6 +7410,256 @@
</sect2>
</sect1>
+ <sect1 id="release-8-1-12">
+ <title>Release 8.1.12</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2008-06-09</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.1.11.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 8.1.12</title>
+
+ <para>
+ A dump/restore is not required for those running 8.1.X.
+ However, if you are upgrading from a version earlier than 8.1.2,
+ see the release notes for 8.1.2.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix <command>ALTER TABLE ADD COLUMN ... PRIMARY KEY</command> so that the new
+ column is correctly checked to see if it's been initialized to all
+ non-nulls (Brendan Jurd)
+ </para>
+
+ <para>
+ Previous versions neglected to check this requirement at all.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible <command>CREATE TABLE</command> failure when inheriting the
+ <quote>same</quote> constraint from multiple parent relations that
+ inherited that constraint from a common ancestor (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix conversions between ISO-8859-5 and other encodings to handle
+ Cyrillic <quote>Yo</quote> characters (<literal>e</literal> and <literal>E</literal> with
+ two dots) (Sergey Burladyan)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix a few datatype input functions
+ that were allowing unused bytes in their results to contain
+ uninitialized, unpredictable values (Tom)
+ </para>
+
+ <para>
+ This could lead to failures in which two apparently identical literal
+ values were not seen as equal, resulting in the parser complaining
+ about unmatched <literal>ORDER BY</literal> and <literal>DISTINCT</literal>
+ expressions.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix a corner case in regular-expression substring matching
+ (<literal>substring(<replaceable>string</replaceable> from
+ <replaceable>pattern</replaceable>)</literal>) (Tom)
+ </para>
+
+ <para>
+ The problem occurs when there is a match to the pattern overall but
+ the user has specified a parenthesized subexpression and that
+ subexpression hasn't got a match. An example is
+ <literal>substring('foo' from 'foo(bar)?')</literal>.
+ This should return NULL, since <literal>(bar)</literal> isn't matched, but
+ it was mistakenly returning the whole-pattern match instead (ie,
+ <literal>foo</literal>).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2008c (for
+ DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba,
+ Argentina/San_Luis, and Chile)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect result from <application>ecpg</application>'s
+ <function>PGTYPEStimestamp_sub()</function> function (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix core dump in <filename>contrib/xml2</filename>'s
+ <function>xpath_table()</function> function when the input query returns a
+ NULL value (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <filename>contrib/xml2</filename>'s makefile to not override
+ <literal>CFLAGS</literal> (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <literal>DatumGetBool</literal> macro to not fail with <application>gcc</application>
+ 4.3 (Tom)
+ </para>
+
+ <para>
+ This problem affects <quote>old style</quote> (V0) C functions that
+ return boolean. The fix is already in 8.3, but the need to
+ back-patch it was not realized at the time.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix longstanding <command>LISTEN</command>/<command>NOTIFY</command>
+ race condition (Tom)
+ </para>
+
+ <para>
+ In rare cases a session that had just executed a
+ <command>LISTEN</command> might not get a notification, even though
+ one would be expected because the concurrent transaction executing
+ <command>NOTIFY</command> was observed to commit later.
+ </para>
+
+ <para>
+ A side effect of the fix is that a transaction that has executed
+ a not-yet-committed <command>LISTEN</command> command will not see any
+ row in <structname>pg_listener</structname> for the <command>LISTEN</command>,
+ should it choose to look; formerly it would have. This behavior
+ was never documented one way or the other, but it is possible that
+ some applications depend on the old behavior.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Disallow <command>LISTEN</command> and <command>UNLISTEN</command> within a
+ prepared transaction (Tom)
+ </para>
+
+ <para>
+ This was formerly allowed but trying to do it had various unpleasant
+ consequences, notably that the originating backend could not exit
+ as long as an <command>UNLISTEN</command> remained uncommitted.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix rare crash when an error occurs during a query using a hash index
+ (Heikki)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix input of datetime values for February 29 in years BC (Tom)
+ </para>
+
+ <para>
+ The former coding was mistaken about which years were leap years.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <quote>unrecognized node type</quote> error in some variants of
+ <command>ALTER OWNER</command> (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>pg_ctl</application> to correctly extract the postmaster's port
+ number from command-line options (Itagaki Takahiro, Tom)
+ </para>
+
+ <para>
+ Previously, <literal>pg_ctl start -w</literal> could try to contact the
+ postmaster on the wrong port, leading to bogus reports of startup
+ failure.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use <option>-fwrapv</option> to defend against possible misoptimization
+ in recent <application>gcc</application> versions (Tom)
+ </para>
+
+ <para>
+ This is known to be necessary when building <productname>PostgreSQL</productname>
+ with <application>gcc</application> 4.3 or later.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix display of constant expressions in <literal>ORDER BY</literal>
+ and <literal>GROUP BY</literal> (Tom)
+ </para>
+
+ <para>
+ An explictly casted constant would be shown incorrectly. This could
+ for example lead to corruption of a view definition during
+ dump and reload.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>libpq</application> to handle NOTICE messages correctly
+ during COPY OUT (Tom)
+ </para>
+
+ <para>
+ This failure has only been observed to occur when a user-defined
+ datatype's output routine issues a NOTICE, but there is no
+ guarantee it couldn't happen due to other causes.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-1-11">
<title>Version 8.1.11</title>
@@ -6845,6 +7671,8 @@
<para>
Cette version contient divers correctifs de la version 8.1.10,
et inclut des correctifs d'importantes failles de sécurité.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<para>
@@ -7121,6 +7949,8 @@
<para>
Cette version contient divers correctifs de la version 8.1.9.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<sect2>
@@ -7243,6 +8073,8 @@
<para>
Cette version contient quelques corrections de la 8.1.8, dont la
correction d'une faille de sécurité.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<sect2>
@@ -7335,6 +8167,8 @@
<para>
Cette version contient une correction de la 8.1.7.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<sect2>
@@ -7376,6 +8210,8 @@
<para>
Cette version contient quelques corrections de la 8.1.6, dont la
correction d'une faille de sécurité.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<sect2>
@@ -7473,6 +8309,8 @@
<para>
Cette version contient quelques corrections de la 8.1.5.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<sect2>
@@ -7627,6 +8465,8 @@
<para>
Cette version contient quelques corrections de la 8.1.4.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<sect2>
@@ -7705,6 +8545,8 @@
<para>
Cette version contient quelques corrections de la 8.1.3 incluant des
correctifs pour des problèmes de sécurité extrêmement sérieux.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<sect2>
@@ -7867,6 +8709,8 @@
<para>
Cette version contient quelques corrections de la 8.1.2 et un très sérieux
problème de sécurité.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<sect2>
@@ -7994,6 +8838,8 @@
<para>
Cette version contient quelques corrections de la version 8.1.1.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<sect2>
@@ -8103,6 +8949,8 @@
<para>
Cette version contient quelques corrections vers la 8.1.0.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<sect2>
@@ -10356,6 +11204,243 @@
</sect2>
</sect1>
+ <sect1 id="release-8-0-16">
+ <title>Release 8.0.16</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2008-06-09</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.0.15.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 8.0.16</title>
+
+ <para>
+ A dump/restore is not required for those running 8.0.X.
+ However, if you are upgrading from a version earlier than 8.0.6,
+ see the release notes for 8.0.6.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix <command>ALTER TABLE ADD COLUMN ... PRIMARY KEY</command> so that the new
+ column is correctly checked to see if it's been initialized to all
+ non-nulls (Brendan Jurd)
+ </para>
+
+ <para>
+ Previous versions neglected to check this requirement at all.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible <command>CREATE TABLE</command> failure when inheriting the
+ <quote>same</quote> constraint from multiple parent relations that
+ inherited that constraint from a common ancestor (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix conversions between ISO-8859-5 and other encodings to handle
+ Cyrillic <quote>Yo</quote> characters (<literal>e</literal> and <literal>E</literal> with
+ two dots) (Sergey Burladyan)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix a few datatype input functions
+ that were allowing unused bytes in their results to contain
+ uninitialized, unpredictable values (Tom)
+ </para>
+
+ <para>
+ This could lead to failures in which two apparently identical literal
+ values were not seen as equal, resulting in the parser complaining
+ about unmatched <literal>ORDER BY</literal> and <literal>DISTINCT</literal>
+ expressions.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix a corner case in regular-expression substring matching
+ (<literal>substring(<replaceable>string</replaceable> from
+ <replaceable>pattern</replaceable>)</literal>) (Tom)
+ </para>
+
+ <para>
+ The problem occurs when there is a match to the pattern overall but
+ the user has specified a parenthesized subexpression and that
+ subexpression hasn't got a match. An example is
+ <literal>substring('foo' from 'foo(bar)?')</literal>.
+ This should return NULL, since <literal>(bar)</literal> isn't matched, but
+ it was mistakenly returning the whole-pattern match instead (ie,
+ <literal>foo</literal>).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2008c (for
+ DST law changes in Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba,
+ Argentina/San_Luis, and Chile)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect result from <application>ecpg</application>'s
+ <function>PGTYPEStimestamp_sub()</function> function (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix core dump in <filename>contrib/xml2</filename>'s
+ <function>xpath_table()</function> function when the input query returns a
+ NULL value (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <filename>contrib/xml2</filename>'s makefile to not override
+ <literal>CFLAGS</literal> (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <literal>DatumGetBool</literal> macro to not fail with <application>gcc</application>
+ 4.3 (Tom)
+ </para>
+
+ <para>
+ This problem affects <quote>old style</quote> (V0) C functions that
+ return boolean. The fix is already in 8.3, but the need to
+ back-patch it was not realized at the time.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix longstanding <command>LISTEN</command>/<command>NOTIFY</command>
+ race condition (Tom)
+ </para>
+
+ <para>
+ In rare cases a session that had just executed a
+ <command>LISTEN</command> might not get a notification, even though
+ one would be expected because the concurrent transaction executing
+ <command>NOTIFY</command> was observed to commit later.
+ </para>
+
+ <para>
+ A side effect of the fix is that a transaction that has executed
+ a not-yet-committed <command>LISTEN</command> command will not see any
+ row in <structname>pg_listener</structname> for the <command>LISTEN</command>,
+ should it choose to look; formerly it would have. This behavior
+ was never documented one way or the other, but it is possible that
+ some applications depend on the old behavior.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix rare crash when an error occurs during a query using a hash index
+ (Heikki)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix input of datetime values for February 29 in years BC (Tom)
+ </para>
+
+ <para>
+ The former coding was mistaken about which years were leap years.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <quote>unrecognized node type</quote> error in some variants of
+ <command>ALTER OWNER</command> (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>pg_ctl</application> to correctly extract the postmaster's port
+ number from command-line options (Itagaki Takahiro, Tom)
+ </para>
+
+ <para>
+ Previously, <literal>pg_ctl start -w</literal> could try to contact the
+ postmaster on the wrong port, leading to bogus reports of startup
+ failure.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use <option>-fwrapv</option> to defend against possible misoptimization
+ in recent <application>gcc</application> versions (Tom)
+ </para>
+
+ <para>
+ This is known to be necessary when building <productname>PostgreSQL</productname>
+ with <application>gcc</application> 4.3 or later.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix display of constant expressions in <literal>ORDER BY</literal>
+ and <literal>GROUP BY</literal> (Tom)
+ </para>
+
+ <para>
+ An explictly casted constant would be shown incorrectly. This could
+ for example lead to corruption of a view definition during
+ dump and reload.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>libpq</application> to handle NOTICE messages correctly
+ during COPY OUT (Tom)
+ </para>
+
+ <para>
+ This failure has only been observed to occur when a user-defined
+ datatype's output routine issues a NOTICE, but there is no
+ guarantee it couldn't happen due to other causes.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-0-15">
<title>Version 8.0.15</title>
@@ -10367,6 +11452,8 @@
<para>
Cette version contient divers correctifs de la version 8.0.14,
et inclut des corrections pour des failles de sécurité importantes.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<para>
@@ -10603,6 +11690,8 @@
<para>
Cette version contient divers correctifs de la version 8.0.13.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -10712,6 +11801,8 @@
<para>
Cette version contient quelques corrections de la 8.0.12, dont la
correction d'une faille de sécurité.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -10789,6 +11880,8 @@
<para>
Cette version contient une correction de la 8.0.11.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -10830,6 +11923,8 @@
<para>
Cette version contient quelques corrections de la 8.0.10, dont la
correction d'une faille de sécurité.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -10899,6 +11994,8 @@
<para>
Cette version contient quelques corrections de la 8.0.9.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -11020,6 +12117,8 @@
<para>
Cette version contient quelques corrections de la 8.0.8.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -11077,6 +12176,8 @@
<para>
Cette version contient quelques corrections de la 8.0.7 incluant des
correctifs pour des problèmes de sécurité extrêmement sérieux.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -11191,6 +12292,8 @@
<para>
Cette version contient quelques corrections de la 8.0.6.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -11294,6 +12397,8 @@
<para>
Cette version contient quelques corrections de la version 8.0.5.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -11385,6 +12490,8 @@
<para>
Cette version contient quelques corrections sur la 8.0.4.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -11466,6 +12573,8 @@
<para>
Cette version contient quelques corrections de la 8.0.3.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -11562,6 +12671,8 @@
<para>
Cette version contient quelques corrections sur la 8.0.2, dont des
correctifs sur des failles de sécurité.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -11683,6 +12794,8 @@
<para>
Cette version contient quelques corrections de la 8.0.1.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -11851,6 +12964,8 @@
<para>
Cette version contient une grande variété de corrections provenant de la
version 8.0.0, incluant plusieurs problèmes relatifs sur la sécurité.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -14273,6 +15388,151 @@
</sect2>
</sect1>
+ <sect1 id="release-7-4-20">
+ <title>Release 7.4.20</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2008-06-09</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 7.4.19.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 7.4.20</title>
+
+ <para>
+ A dump/restore is not required for those running 7.4.X.
+ However, if you are upgrading from a version earlier than 7.4.11,
+ see the release notes for 7.4.11.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix conversions between ISO-8859-5 and other encodings to handle
+ Cyrillic <quote>Yo</quote> characters (<literal>e</literal> and <literal>E</literal> with
+ two dots) (Sergey Burladyan)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix a few datatype input functions
+ that were allowing unused bytes in their results to contain
+ uninitialized, unpredictable values (Tom)
+ </para>
+
+ <para>
+ This could lead to failures in which two apparently identical literal
+ values were not seen as equal, resulting in the parser complaining
+ about unmatched <literal>ORDER BY</literal> and <literal>DISTINCT</literal>
+ expressions.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix a corner case in regular-expression substring matching
+ (<literal>substring(<replaceable>string</replaceable> from
+ <replaceable>pattern</replaceable>)</literal>) (Tom)
+ </para>
+
+ <para>
+ The problem occurs when there is a match to the pattern overall but
+ the user has specified a parenthesized subexpression and that
+ subexpression hasn't got a match. An example is
+ <literal>substring('foo' from 'foo(bar)?')</literal>.
+ This should return NULL, since <literal>(bar)</literal> isn't matched, but
+ it was mistakenly returning the whole-pattern match instead (ie,
+ <literal>foo</literal>).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect result from <application>ecpg</application>'s
+ <function>PGTYPEStimestamp_sub()</function> function (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <literal>DatumGetBool</literal> macro to not fail with <application>gcc</application>
+ 4.3 (Tom)
+ </para>
+
+ <para>
+ This problem affects <quote>old style</quote> (V0) C functions that
+ return boolean. The fix is already in 8.3, but the need to
+ back-patch it was not realized at the time.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix longstanding <command>LISTEN</command>/<command>NOTIFY</command>
+ race condition (Tom)
+ </para>
+
+ <para>
+ In rare cases a session that had just executed a
+ <command>LISTEN</command> might not get a notification, even though
+ one would be expected because the concurrent transaction executing
+ <command>NOTIFY</command> was observed to commit later.
+ </para>
+
+ <para>
+ A side effect of the fix is that a transaction that has executed
+ a not-yet-committed <command>LISTEN</command> command will not see any
+ row in <structname>pg_listener</structname> for the <command>LISTEN</command>,
+ should it choose to look; formerly it would have. This behavior
+ was never documented one way or the other, but it is possible that
+ some applications depend on the old behavior.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix display of constant expressions in <literal>ORDER BY</literal>
+ and <literal>GROUP BY</literal> (Tom)
+ </para>
+
+ <para>
+ An explictly casted constant would be shown incorrectly. This could
+ for example lead to corruption of a view definition during
+ dump and reload.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>libpq</application> to handle NOTICE messages correctly
+ during COPY OUT (Tom)
+ </para>
+
+ <para>
+ This failure has only been observed to occur when a user-defined
+ datatype's output routine issues a NOTICE, but there is no
+ guarantee it couldn't happen due to other causes.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-7-4-19">
<title>Version 7.4.19</title>
@@ -14284,6 +15544,8 @@
<para>
Cette version contient divers correctifs de la version 7.4.18,
et inclut des corrections pour des failles de sécurité importantes.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -14449,6 +15711,8 @@
<para>
Cette version contient divers correctifs de la version 7.4.17.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -14522,6 +15786,8 @@
<para>
Cette version contient quelques corrections de la 7.4.16, dont la
correction d'une faille de sécurité.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -14593,6 +15859,8 @@
<para>
Cette version contient quelques corrections de la 7.4.15, dont la
correction d'une faille de sécurité.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -14662,6 +15930,8 @@
<para>
Cette version contient quelques corrections de la 7.4.14.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -14753,6 +16023,8 @@
<para>
Cette version contient quelques corrections de la 7.4.13.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -14800,6 +16072,8 @@
<para>
Cette version contient quelques corrections de la 7.4.12 incluant des
correctifs pour des problèmes de sécurité extrêmement sérieux.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -14908,6 +16182,8 @@
<para>
Cette version contient quelques corrections de la 7.4.11.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -14970,6 +16246,8 @@
<para>
Cette version contient quelques corrections de la version 7.4.10.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -15041,6 +16319,8 @@
<para>
Cette version contient quelques corrections sur la 7.4.9.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -15094,6 +16374,8 @@
<para>
Cette version contient quelques corrections de la 7.4.8.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -15168,6 +16450,8 @@
<para>
Cette version contient quelques corrections sur la 7.4.7, dont des
correctifs sur des failles de sécurité.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -15354,6 +16638,8 @@
<para>
Cette version contient une variété de corrections de la version 7.4.6,
incluant des correctifs de sécurité.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -15416,6 +16702,8 @@
<para>
Cette version contient plusieurs correctifs de la version 7.4.5.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
@@ -15499,6 +16787,8 @@
<para>
Cette version contient la correction d'un bogue sérieux de la version 7.4.4.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
@@ -15538,6 +16828,8 @@
<para>
Cette version contient quelques correctifs sur la 7.4.3.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
@@ -15599,6 +16891,8 @@
<para>
Cette version contient quelques correctifs pour la 7.4.2.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
@@ -15673,6 +16967,8 @@
<para>
Cette version contient quelques correctifs pour la 7.4.1.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
@@ -15827,6 +17123,8 @@
<para>
Cette version contient plusieurs correctifs de la 7.4.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
Modified: traduc/trunk/postgresql/version.xml
===================================================================
--- traduc/trunk/postgresql/version.xml 2008-06-06 13:20:04 UTC (rev 1058)
+++ traduc/trunk/postgresql/version.xml 2008-06-06 13:51:27 UTC (rev 1059)
@@ -1,2 +1,2 @@
-<!ENTITY version "8.3.1">
+<!ENTITY version "8.3.2">
<!ENTITY majorversion "8.3">
Modified: traduc/trunk/postgresql/xml2.xml
===================================================================
--- traduc/trunk/postgresql/xml2.xml 2008-06-06 13:20:04 UTC (rev 1058)
+++ traduc/trunk/postgresql/xml2.xml 2008-06-06 13:51:27 UTC (rev 1059)
@@ -392,9 +392,7 @@
<title>Fonctions XSLT</title>
<para>
- Les fonctions suivantes sont disponibles si libxslt est installé (ceci
- n'est pas détecté automatiquement, donc vous aurez besoin de corriger le
- Makefile).
+ Les fonctions suivantes sont disponibles si libxslt est installé.
</para>
<sect3>
More information about the Trad
mailing list