[Trad] [svn:pgfr] r1055 - in traduc/branches/bv81x/manuel: . ref
svncommit at kryskool.org
svncommit at kryskool.org
Ven 6 Juin 14:57:22 CEST 2008
Auteur: gleu
Date: 2008-06-06 14:57:20 +0200 (ven, 06 jun 2008)
Nouvelle Révision: 1055
Modification:
traduc/branches/bv81x/manuel/protocol.xml
traduc/branches/bv81x/manuel/ref/grant.xml
traduc/branches/bv81x/manuel/ref/prepare_transaction.xml
traduc/branches/bv81x/manuel/release.xml
traduc/branches/bv81x/manuel/version.xml
Log:
Mise à jour version 8.1.12.
Modified: traduc/branches/bv81x/manuel/protocol.xml
===================================================================
--- traduc/branches/bv81x/manuel/protocol.xml 2008-06-06 12:34:57 UTC (rev 1054)
+++ traduc/branches/bv81x/manuel/protocol.xml 2008-06-06 12:57:20 UTC (rev 1055)
@@ -978,14 +978,22 @@
CopyData et CopyDone non souhaités.
</para>
- <para>
- Si le serveur détecte une erreur en mode Copy-out, il enverra un message
- ErrorResponse et retournera dans le mode de traitement normal. Le client
- devrait traiter la réception d'un message ErrorResponse (ou en fait tout
- type de message autre que CopyData ou CopyDone) par la clôture du mode
- Copy-out.
- </para>
+ <para>
+ Si le serveur détecte une erreur en mode Copy-out, il enverra un message
+ ErrorResponse et retournera dans le mode de traitement normal. Le client
+ devrait traiter la réception d'un message ErrorResponse comme terminant
+ le mode <quote>copy-out</quote>.
+ </para>
+ <para>
+ Il est possible que les messages NoticeResponse et ParameterStatus soient
+ entremêlés avec des messages CopyData ; les interfaces doivent gérer
+ ce cas, et devraient être aussi préparées à d'autres types de messages
+ asynchrones (voir <xref linkend="protocol-async"/>). Sinon, tout type
+ de message autre que CopyData et CopyDone pourrait être traité comme
+ terminant le mode copy-out.
+ </para>
+
<para>
Les messages CopyInResponse et CopyOutResponse incluent les champs qui
informent le client du nombre de colonnes par ligne et des codes de format
Modified: traduc/branches/bv81x/manuel/ref/grant.xml
===================================================================
--- traduc/branches/bv81x/manuel/ref/grant.xml 2008-06-06 12:34:57 UTC (rev 1054)
+++ traduc/branches/bv81x/manuel/ref/grant.xml 2008-06-06 12:57:20 UTC (rev 1055)
@@ -134,10 +134,14 @@
<term>SELECT</term>
<listitem>
<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
+ Autorise <xref linkend="sql-select" endterm="sql-select-title"/> parmi
+ toutes les colonnes de la table, vue ou séquence spécifiée. Autorise
+ 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 permet 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>
@@ -235,7 +246,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/branches/bv81x/manuel/ref/prepare_transaction.xml
===================================================================
--- traduc/branches/bv81x/manuel/ref/prepare_transaction.xml 2008-06-06 12:34:57 UTC (rev 1054)
+++ traduc/branches/bv81x/manuel/ref/prepare_transaction.xml 2008-06-06 12:57:20 UTC (rev 1055)
@@ -89,10 +89,11 @@
<para>
Il n'est actuellement pas possible de préparer (<command>PREPARE</command>) une
- transaction qui a exécuté des opérations impliquant des tables temporaires ou
- qui a créé des curseurs <literal>WITH HOLD</literal>. Ces fonctionnalités sont trop
- intégrées à la session en cours pour avoir la moindre utilité dans une transaction
- préparée.
+ transaction qui a exécuté des opérations impliquant des tables temporaires,
+ qui a créé des curseurs <literal>WITH HOLD</literal>, ou exécuté les
+ commandes <command>LISTEN</command> ou <command>UNLISTEN</command>.. Ces
+ fonctionnalités sont trop intégrées à la session en cours pour avoir la
+ moindre utilité dans une transaction préparée.
</para>
<para>
Modified: traduc/branches/bv81x/manuel/release.xml
===================================================================
--- traduc/branches/bv81x/manuel/release.xml 2008-06-06 12:34:57 UTC (rev 1054)
+++ traduc/branches/bv81x/manuel/release.xml 2008-06-06 12:57:20 UTC (rev 1055)
@@ -35,6 +35,284 @@
<appendix id="release">
<title>Notes de version</title>
+ <para>
+ The release notes contain the significant changes in each
+ <productname>PostgreSQL</productname> release, with major features and migration
+ issues listed at the top. The release notes do not contain changes
+ that affect only a few users or changes that are internal and therefore not
+ user-visible. For example, the optimizer is improved in almost every
+ release, but the improvements are usually observed by users as simply
+ faster queries.
+ </para>
+
+ <para>
+ A complete list of changes for each release can be obtained by
+ viewing the <link linkend="cvs">CVS</link> logs for each release.
+ The <ulink
+ url="http://archives.postgresql.org/pgsql-committers/">pgsql-committers
+ email list</ulink> contains all source code changes as well. There is also
+ a <ulink url="http://developer.postgresql.org/cvsweb.cgi/pgsql/">web
+ interface</ulink> that shows changes to specific files.
+ <!-- we need a file containing the CVS logs for each release, and something
+ like the SVN web interface that groups commits but has branches -->
+ </para>
+
+ <para>
+ The name appearing next to each item represents the major developer for
+ that item. Of course all changes involve community discussion and patch
+ review, so each item is truly a community effort.
+ </para>
+
+ <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>
@@ -46,6 +324,8 @@
<para>
Cette version contient divers correctifs de la version 8.1.10,
et inclut des corrections pour des failles de sécurité importantes.
+ For information about new features in the 8.1 major release, see
+ <xref linkend="release-8-1"/>.
</para>
<para>
@@ -322,6 +602,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>
@@ -452,6 +734,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>
@@ -544,6 +828,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>
@@ -585,6 +871,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>
@@ -682,6 +970,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>
@@ -836,6 +1126,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>
@@ -913,6 +1205,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>
@@ -1069,6 +1363,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>
@@ -1196,6 +1492,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>
@@ -1305,6 +1603,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>
@@ -3512,6 +3812,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>
@@ -3523,6 +4060,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>
@@ -3759,6 +4298,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>
@@ -3876,6 +4417,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>
@@ -3953,6 +4496,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>
@@ -3994,6 +4539,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>
@@ -4063,6 +4610,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>
@@ -4184,6 +4733,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>
@@ -4241,6 +4792,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>
@@ -4355,6 +4908,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>
@@ -4458,6 +5013,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>
@@ -4549,6 +5106,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>
@@ -4630,6 +5189,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>
@@ -4726,6 +5287,8 @@
<para>
Cette version contient quelques corrections sur la 8.0.2, dont des
correctifs sur des trous de sécurité.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
</para>
<sect2>
@@ -4847,6 +5410,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>
@@ -5015,6 +5580,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>
@@ -7437,6 +8004,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>
@@ -7448,6 +8160,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>
@@ -7613,6 +8327,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>
@@ -7694,6 +8410,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>
@@ -7765,6 +8483,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>
@@ -7834,6 +8554,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>
@@ -7925,6 +8647,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>
@@ -7972,6 +8696,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>
@@ -8080,6 +8806,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>
@@ -8142,6 +8870,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>
@@ -8213,6 +8943,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>
@@ -8266,6 +8998,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>
@@ -8340,6 +9074,8 @@
<para>
Cette version contient quelques corrections sur la 7.4.7, dont des
correctifs sur des trous de sécurité.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
</para>
<sect2>
@@ -8526,6 +9262,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>
@@ -8588,6 +9326,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>
@@ -8671,6 +9411,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>
@@ -8710,6 +9452,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>
@@ -8771,6 +9515,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>
@@ -8845,6 +9591,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>
@@ -8999,6 +9747,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/branches/bv81x/manuel/version.xml
===================================================================
--- traduc/branches/bv81x/manuel/version.xml 2008-06-06 12:34:57 UTC (rev 1054)
+++ traduc/branches/bv81x/manuel/version.xml 2008-06-06 12:57:20 UTC (rev 1055)
@@ -1,2 +1,2 @@
-<!ENTITY version "8.1.11">
+<!ENTITY version "8.1.12">
<!ENTITY majorversion "8.1">
More information about the Trad
mailing list