[Trad] [svn:pgfr] r1478 - in traduc/branches/bv83x: . ref
admin at listes.postgresql.fr
admin at listes.postgresql.fr
Sam 13 Mar 16:10:56 CET 2010
Author: gleu
Date: 2010-03-13 16:10:56 +0100 (Sat, 13 Mar 2010)
New Revision: 1478
Modified:
traduc/branches/bv83x/config.xml
traduc/branches/bv83x/pgstandby.xml
traduc/branches/bv83x/ref/psql-ref.xml
traduc/branches/bv83x/release-7.4.xml
traduc/branches/bv83x/release-8.0.xml
traduc/branches/bv83x/release-8.1.xml
traduc/branches/bv83x/release-8.2.xml
traduc/branches/bv83x/release-8.3.xml
traduc/branches/bv83x/version.xml
Log:
Mise ?\195?\160 jour en version 8.3.10.
Modified: traduc/branches/bv83x/config.xml
===================================================================
--- traduc/branches/bv83x/config.xml 2010-03-13 15:01:57 UTC (rev 1477)
+++ traduc/branches/bv83x/config.xml 2010-03-13 15:10:56 UTC (rev 1478)
@@ -609,6 +609,36 @@
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><varname>ssl_renegotiation_limit</varname> (<type>int</type>)</term>
+ <indexterm>
+ <primary>paramètre de configuration <varname>ssl_renegotiation_limit</varname></primary>
+ </indexterm>
+ <listitem>
+ <para>
+ Indique la quantité de données pouvant transiter sur une connexion
+ en <acronym>SSL</acronym> avant qu'une renégotiation de la session ne
+ survienne. La renégotiation de la session diminue le risque d'analyse
+ du chiffrement lorsque de gros volumes de données sont envoyées mais
+ cela a un coût important pour les performances. Les données émises et
+ réceptionnées sont prises en compte lors de la vérification de la
+ limite. Si ce paramètre est à 0, la renégotiation est désactivée. La
+ valeur par défaut est de <literal>512 Mo</literal>.
+ </para>
+ <note>
+ <para>
+ Les bibliothèques SSL antérieures à novembre 2009 ne sont pas
+ sécurisées lors de l'utilisation de la renégotiation SSL à cause d'une
+ faille dans le protocole SSL. Pour corriger rapidement cette faille,
+ certains fournisseurs de la bibliothèque ont proposé des bibliothèques
+ SSL ne disposant plus de la fonctionnalité de renégotiation. Si une de
+ ces bibliothèques sont utilisées sur le serveur ou sur le client, la
+ renégotiation SSL doit être désactivée.
+ </para>
+ </note>
+ </listitem>
+ </varlistentry>
+
<varlistentry id="guc-password-encryption"
xreflabel="password_encryption">
<term><varname>password_encryption</varname> (<type>boolean</type>)</term>
Modified: traduc/branches/bv83x/pgstandby.xml
===================================================================
--- traduc/branches/bv83x/pgstandby.xml 2010-03-13 15:01:57 UTC (rev 1477)
+++ traduc/branches/bv83x/pgstandby.xml 2010-03-13 15:10:56 UTC (rev 1478)
@@ -217,6 +217,15 @@
</tbody>
</tgroup>
</table>
+ <caution>
+ <para>
+ Il est essentiel que le fichier trigger soit créé avec des droits
+ permettant au processus postgres de supprimer ce fichier. Généralement,
+ cela se fait en créant le fichier à partir du compte utilisateur
+ postgres. Si ce n'est pas fait, cela empêchera la fin de la restauration
+ des journaux de transactions et la mise en ligne du serveur PostgreSQL.
+ </para>
+ </caution>
<note>
<para>
<literal>--help</literal> n'est pas accepté car
Modified: traduc/branches/bv83x/ref/psql-ref.xml
===================================================================
--- traduc/branches/bv83x/ref/psql-ref.xml 2010-03-13 15:01:57 UTC (rev 1477)
+++ traduc/branches/bv83x/ref/psql-ref.xml 2010-03-13 15:10:56 UTC (rev 1478)
@@ -741,7 +741,7 @@
<tip>
<para>
Pour afficher votre répertoire courant, utilisez
- <literal>\!pwd</literal>.
+ <literal>\! pwd</literal>.
</para>
</tip>
</listitem>
Modified: traduc/branches/bv83x/release-7.4.xml
===================================================================
--- traduc/branches/bv83x/release-7.4.xml 2010-03-13 15:01:57 UTC (rev 1477)
+++ traduc/branches/bv83x/release-7.4.xml 2010-03-13 15:10:56 UTC (rev 1478)
@@ -4,6 +4,125 @@
par $Author: gleu $
révision $Revision: 1317 $ -->
+ <sect1 id="release-7-4-28">
+ <title>Release 7.4.28</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2010-03-15</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 7.4.27.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
+ </para>
+
+ <para>
+ The <productname>PostgreSQL</productname> community will stop releasing updates
+ for the 7.4.X release series in July 2010.
+ Users are encouraged to update to a newer release branch soon.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 7.4.28</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.26,
+ see the release notes for 7.4.26.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Add new configuration parameter <varname>ssl_renegotiation_limit</varname> to
+ control how often we do session key renegotiation for an SSL connection
+ (Magnus)
+ </para>
+
+ <para>
+ This can be set to zero to disable renegotiation completely, which may
+ be required if a broken SSL library is used. In particular, some
+ vendors are shipping stopgap patches for CVE-2009-3555 that cause
+ renegotiation attempts to fail.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <function>substring()</function> for <type>bit</type> types treat any negative
+ length as meaning <quote>all the rest of the string</quote> (Tom)
+ </para>
+
+ <para>
+ The previous coding treated only -1 that way, and would produce an
+ invalid result value for other negative values, possibly leading to
+ a crash (CVE-2010-0442).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix some cases of pathologically slow regular expression matching (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When reading <filename>pg_hba.conf</filename> and related files, do not treat
+ <literal>@something</literal> as a file inclusion request if the <literal>@</literal>
+ appears inside quote marks; also, never treat <literal>@</literal> by itself
+ as a file inclusion request (Tom)
+ </para>
+
+ <para>
+ This prevents erratic behavior if a role or database name starts with
+ <literal>@</literal>. If you need to include a file whose path name
+ contains spaces, you can still do so, but you must write
+ <literal>@"/path to/file"</literal> rather than putting the quotes around
+ the whole construct.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent infinite loop on some platforms if a directory is named as
+ an inclusion target in <filename>pg_hba.conf</filename> and related files
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
+ </para>
+
+ <para>
+ The only known symptom of this oversight is that the Tcl
+ <literal>clock</literal> command misbehaves if using Tcl 8.5 or later.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent crash in <filename>contrib/dblink</filename> when too many key
+ columns are specified to a <function>dblink_build_sql_*</function> function
+ (Rushabh Lathia, Joe Conway)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-7-4-27">
<title>Release 7.4.27</title>
Modified: traduc/branches/bv83x/release-8.0.xml
===================================================================
--- traduc/branches/bv83x/release-8.0.xml 2010-03-13 15:01:57 UTC (rev 1477)
+++ traduc/branches/bv83x/release-8.0.xml 2010-03-13 15:10:56 UTC (rev 1478)
@@ -4,6 +4,183 @@
par $Author: gleu $
révision $Revision: 1317 $ -->
+ <sect1 id="release-8-0-24">
+ <title>Release 8.0.24</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2010-03-15</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.0.23.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
+ </para>
+
+ <para>
+ The <productname>PostgreSQL</productname> community will stop releasing updates
+ for the 8.0.X release series in July 2010.
+ Users are encouraged to update to a newer release branch soon.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 8.0.24</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.22,
+ see the release notes for 8.0.22.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Add new configuration parameter <varname>ssl_renegotiation_limit</varname> to
+ control how often we do session key renegotiation for an SSL connection
+ (Magnus)
+ </para>
+
+ <para>
+ This can be set to zero to disable renegotiation completely, which may
+ be required if a broken SSL library is used. In particular, some
+ vendors are shipping stopgap patches for CVE-2009-3555 that cause
+ renegotiation attempts to fail.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crashes when trying to recover from a failure in
+ subtransaction start (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix server memory leak associated with use of savepoints and a client
+ encoding different from server's encoding (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <function>substring()</function> for <type>bit</type> types treat any negative
+ length as meaning <quote>all the rest of the string</quote> (Tom)
+ </para>
+
+ <para>
+ The previous coding treated only -1 that way, and would produce an
+ invalid result value for other negative values, possibly leading to
+ a crash (CVE-2010-0442).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix integer-to-bit-string conversions to handle the first fractional
+ byte correctly when the output bit width is wider than the given
+ integer by something other than a multiple of 8 bits (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix some cases of pathologically slow regular expression matching (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix the <literal>STOP WAL LOCATION</literal> entry in backup history files to
+ report the next WAL segment's name when the end location is exactly at a
+ segment boundary (Itagaki Takahiro)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When reading <filename>pg_hba.conf</filename> and related files, do not treat
+ <literal>@something</literal> as a file inclusion request if the <literal>@</literal>
+ appears inside quote marks; also, never treat <literal>@</literal> by itself
+ as a file inclusion request (Tom)
+ </para>
+
+ <para>
+ This prevents erratic behavior if a role or database name starts with
+ <literal>@</literal>. If you need to include a file whose path name
+ contains spaces, you can still do so, but you must write
+ <literal>@"/path to/file"</literal> rather than putting the quotes around
+ the whole construct.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent infinite loop on some platforms if a directory is named as
+ an inclusion target in <filename>pg_hba.conf</filename> and related files
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix plpgsql failure in one case where a composite column is set to NULL
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add <literal>volatile</literal> markings in PL/Python to avoid possible
+ compiler-specific misbehavior (Zdenek Kotala)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
+ </para>
+
+ <para>
+ The only known symptom of this oversight is that the Tcl
+ <literal>clock</literal> command misbehaves if using Tcl 8.5 or later.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent crash in <filename>contrib/dblink</filename> when too many key
+ columns are specified to a <function>dblink_build_sql_*</function> function
+ (Rushabh Lathia, Joe Conway)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix assorted crashes in <filename>contrib/xml2</filename> caused by sloppy
+ memory management (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2010e
+ for DST law changes in Bangladesh, Chile, Fiji, Mexico, Paraguay, Samoa.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-0-23">
<title>Release 8.0.23</title>
Modified: traduc/branches/bv83x/release-8.1.xml
===================================================================
--- traduc/branches/bv83x/release-8.1.xml 2010-03-13 15:01:57 UTC (rev 1477)
+++ traduc/branches/bv83x/release-8.1.xml 2010-03-13 15:10:56 UTC (rev 1478)
@@ -4,6 +4,196 @@
par $Author: gleu $
révision $Revision: 1317 $ -->
+ <sect1 id="release-8-1-20">
+ <title>Release 8.1.20</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2010-03-15</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.1.19.
+ 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.20</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.18,
+ see the release notes for 8.1.18.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Add new configuration parameter <varname>ssl_renegotiation_limit</varname> to
+ control how often we do session key renegotiation for an SSL connection
+ (Magnus)
+ </para>
+
+ <para>
+ This can be set to zero to disable renegotiation completely, which may
+ be required if a broken SSL library is used. In particular, some
+ vendors are shipping stopgap patches for CVE-2009-3555 that cause
+ renegotiation attempts to fail.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crashes when trying to recover from a failure in
+ subtransaction start (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix server memory leak associated with use of savepoints and a client
+ encoding different from server's encoding (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <function>substring()</function> for <type>bit</type> types treat any negative
+ length as meaning <quote>all the rest of the string</quote> (Tom)
+ </para>
+
+ <para>
+ The previous coding treated only -1 that way, and would produce an
+ invalid result value for other negative values, possibly leading to
+ a crash (CVE-2010-0442).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix integer-to-bit-string conversions to handle the first fractional
+ byte correctly when the output bit width is wider than the given
+ integer by something other than a multiple of 8 bits (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix some cases of pathologically slow regular expression matching (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix the <literal>STOP WAL LOCATION</literal> entry in backup history files to
+ report the next WAL segment's name when the end location is exactly at a
+ segment boundary (Itagaki Takahiro)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix some more cases of temporary-file leakage (Heikki)
+ </para>
+
+ <para>
+ This corrects a problem introduced in the previous minor release.
+ One case that failed is when a plpgsql function returning set is
+ called within another function's exception handler.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When reading <filename>pg_hba.conf</filename> and related files, do not treat
+ <literal>@something</literal> as a file inclusion request if the <literal>@</literal>
+ appears inside quote marks; also, never treat <literal>@</literal> by itself
+ as a file inclusion request (Tom)
+ </para>
+
+ <para>
+ This prevents erratic behavior if a role or database name starts with
+ <literal>@</literal>. If you need to include a file whose path name
+ contains spaces, you can still do so, but you must write
+ <literal>@"/path to/file"</literal> rather than putting the quotes around
+ the whole construct.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent infinite loop on some platforms if a directory is named as
+ an inclusion target in <filename>pg_hba.conf</filename> and related files
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>psql</application>'s <literal>numericlocale</literal> option to not
+ format strings it shouldn't in latex and troff output formats (Heikki)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix plpgsql failure in one case where a composite column is set to NULL
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add <literal>volatile</literal> markings in PL/Python to avoid possible
+ compiler-specific misbehavior (Zdenek Kotala)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
+ </para>
+
+ <para>
+ The only known symptom of this oversight is that the Tcl
+ <literal>clock</literal> command misbehaves if using Tcl 8.5 or later.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent crash in <filename>contrib/dblink</filename> when too many key
+ columns are specified to a <function>dblink_build_sql_*</function> function
+ (Rushabh Lathia, Joe Conway)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix assorted crashes in <filename>contrib/xml2</filename> caused by sloppy
+ memory management (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2010e
+ for DST law changes in Bangladesh, Chile, Fiji, Mexico, Paraguay, Samoa.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-1-19">
<title>Release 8.1.19</title>
Modified: traduc/branches/bv83x/release-8.2.xml
===================================================================
--- traduc/branches/bv83x/release-8.2.xml 2010-03-13 15:01:57 UTC (rev 1477)
+++ traduc/branches/bv83x/release-8.2.xml 2010-03-13 15:10:56 UTC (rev 1478)
@@ -4,6 +4,277 @@
par $Author: gleu $
révision $Revision: 1317 $ -->
+ <sect1 id="release-8-2-16">
+ <title>Release 8.2.16</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2010-03-15</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.2.15.
+ 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.16</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.14,
+ see the release notes for 8.2.14.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Add new configuration parameter <varname>ssl_renegotiation_limit</varname> to
+ control how often we do session key renegotiation for an SSL connection
+ (Magnus)
+ </para>
+
+ <para>
+ This can be set to zero to disable renegotiation completely, which may
+ be required if a broken SSL library is used. In particular, some
+ vendors are shipping stopgap patches for CVE-2009-3555 that cause
+ renegotiation attempts to fail.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible deadlock during backend startup (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crashes due to not handling errors during relcache reload
+ cleanly (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crashes when trying to recover from a failure in
+ subtransaction start (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix server memory leak associated with use of savepoints and a client
+ encoding different from server's encoding (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect WAL data emitted during end-of-recovery cleanup of a GIST
+ index page split (Yoichi Hirai)
+ </para>
+
+ <para>
+ This would result in index corruption, or even more likely an error
+ during WAL replay, if we were unlucky enough to crash during
+ end-of-recovery cleanup after having completed an incomplete GIST
+ insertion.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <function>substring()</function> for <type>bit</type> types treat any negative
+ length as meaning <quote>all the rest of the string</quote> (Tom)
+ </para>
+
+ <para>
+ The previous coding treated only -1 that way, and would produce an
+ invalid result value for other negative values, possibly leading to
+ a crash (CVE-2010-0442).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix integer-to-bit-string conversions to handle the first fractional
+ byte correctly when the output bit width is wider than the given
+ integer by something other than a multiple of 8 bits (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix some cases of pathologically slow regular expression matching (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix the <literal>STOP WAL LOCATION</literal> entry in backup history files to
+ report the next WAL segment's name when the end location is exactly at a
+ segment boundary (Itagaki Takahiro)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix some more cases of temporary-file leakage (Heikki)
+ </para>
+
+ <para>
+ This corrects a problem introduced in the previous minor release.
+ One case that failed is when a plpgsql function returning set is
+ called within another function's exception handler.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve constraint exclusion processing of boolean-variable cases,
+ in particular make it possible to exclude a partition that has a
+ <quote>bool_column = false</quote> constraint (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When reading <filename>pg_hba.conf</filename> and related files, do not treat
+ <literal>@something</literal> as a file inclusion request if the <literal>@</literal>
+ appears inside quote marks; also, never treat <literal>@</literal> by itself
+ as a file inclusion request (Tom)
+ </para>
+
+ <para>
+ This prevents erratic behavior if a role or database name starts with
+ <literal>@</literal>. If you need to include a file whose path name
+ contains spaces, you can still do so, but you must write
+ <literal>@"/path to/file"</literal> rather than putting the quotes around
+ the whole construct.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent infinite loop on some platforms if a directory is named as
+ an inclusion target in <filename>pg_hba.conf</filename> and related files
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible infinite loop if <function>SSL_read</function> or
+ <function>SSL_write</function> fails without setting <varname>errno</varname> (Tom)
+ </para>
+
+ <para>
+ This is reportedly possible with some Windows versions of
+ <application>openssl</application>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>psql</application>'s <literal>numericlocale</literal> option to not
+ format strings it shouldn't in latex and troff output formats (Heikki)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <application>psql</application> return the correct exit status (3) when
+ <literal>ON_ERROR_STOP</literal> and <literal>--single-transaction</literal> are
+ both specified and an error occurs during the implied <command>COMMIT</command>
+ (Bruce)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix plpgsql failure in one case where a composite column is set to NULL
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible failure when calling PL/Perl functions from PL/PerlU
+ or vice versa (Tim Bunce)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add <literal>volatile</literal> markings in PL/Python to avoid possible
+ compiler-specific misbehavior (Zdenek Kotala)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
+ </para>
+
+ <para>
+ The only known symptom of this oversight is that the Tcl
+ <literal>clock</literal> command misbehaves if using Tcl 8.5 or later.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent crash in <filename>contrib/dblink</filename> when too many key
+ columns are specified to a <function>dblink_build_sql_*</function> function
+ (Rushabh Lathia, Joe Conway)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix assorted crashes in <filename>contrib/xml2</filename> caused by sloppy
+ memory management (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make building of <filename>contrib/xml2</filename> more robust on Windows
+ (Andrew)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix race condition in Windows signal handling (Radu Ilie)
+ </para>
+
+ <para>
+ One known symptom of this bug is that rows in <structname>pg_listener</structname>
+ could be dropped under heavy load.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2010e
+ for DST law changes in Bangladesh, Chile, Fiji, Mexico, Paraguay, Samoa.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-2-15">
<title>Release 8.2.15</title>
Modified: traduc/branches/bv83x/release-8.3.xml
===================================================================
--- traduc/branches/bv83x/release-8.3.xml 2010-03-13 15:01:57 UTC (rev 1477)
+++ traduc/branches/bv83x/release-8.3.xml 2010-03-13 15:10:56 UTC (rev 1478)
@@ -4,6 +4,333 @@
par $Author: gleu $
révision $Revision: 1317 $ -->
+ <sect1 id="release-8-3-10">
+ <title>Release 8.3.10</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2010-03-15</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.3.9.
+ 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.10</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.8,
+ see the release notes for 8.3.8.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Add new configuration parameter <varname>ssl_renegotiation_limit</varname> to
+ control how often we do session key renegotiation for an SSL connection
+ (Magnus)
+ </para>
+
+ <para>
+ This can be set to zero to disable renegotiation completely, which may
+ be required if a broken SSL library is used. In particular, some
+ vendors are shipping stopgap patches for CVE-2009-3555 that cause
+ renegotiation attempts to fail.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible deadlock during backend startup (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crashes due to not handling errors during relcache reload
+ cleanly (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crash due to use of dangling pointer to a cached plan
+ (Tatsuo)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crashes when trying to recover from a failure in
+ subtransaction start (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix server memory leak associated with use of savepoints and a client
+ encoding different from server's encoding (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect WAL data emitted during end-of-recovery cleanup of a GIST
+ index page split (Yoichi Hirai)
+ </para>
+
+ <para>
+ This would result in index corruption, or even more likely an error
+ during WAL replay, if we were unlucky enough to crash during
+ end-of-recovery cleanup after having completed an incomplete GIST
+ insertion.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <function>substring()</function> for <type>bit</type> types treat any negative
+ length as meaning <quote>all the rest of the string</quote> (Tom)
+ </para>
+
+ <para>
+ The previous coding treated only -1 that way, and would produce an
+ invalid result value for other negative values, possibly leading to
+ a crash (CVE-2010-0442).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix integer-to-bit-string conversions to handle the first fractional
+ byte correctly when the output bit width is wider than the given
+ integer by something other than a multiple of 8 bits (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix some cases of pathologically slow regular expression matching (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix assorted crashes in <type>xml</type> processing caused by sloppy
+ memory management (Tom)
+ </para>
+
+ <para>
+ This is a back-patch of changes first applied in 8.4. The 8.3 code
+ was known buggy, but the new code was sufficiently different to not
+ want to back-patch it until it had gotten some field testing.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix bug with trying to update a field of an element of a
+ composite-type array column (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix the <literal>STOP WAL LOCATION</literal> entry in backup history files to
+ report the next WAL segment's name when the end location is exactly at a
+ segment boundary (Itagaki Takahiro)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix some more cases of temporary-file leakage (Heikki)
+ </para>
+
+ <para>
+ This corrects a problem introduced in the previous minor release.
+ One case that failed is when a plpgsql function returning set is
+ called within another function's exception handler.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve constraint exclusion processing of boolean-variable cases,
+ in particular make it possible to exclude a partition that has a
+ <quote>bool_column = false</quote> constraint (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When reading <filename>pg_hba.conf</filename> and related files, do not treat
+ <literal>@something</literal> as a file inclusion request if the <literal>@</literal>
+ appears inside quote marks; also, never treat <literal>@</literal> by itself
+ as a file inclusion request (Tom)
+ </para>
+
+ <para>
+ This prevents erratic behavior if a role or database name starts with
+ <literal>@</literal>. If you need to include a file whose path name
+ contains spaces, you can still do so, but you must write
+ <literal>@"/path to/file"</literal> rather than putting the quotes around
+ the whole construct.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent infinite loop on some platforms if a directory is named as
+ an inclusion target in <filename>pg_hba.conf</filename> and related files
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible infinite loop if <function>SSL_read</function> or
+ <function>SSL_write</function> fails without setting <varname>errno</varname> (Tom)
+ </para>
+
+ <para>
+ This is reportedly possible with some Windows versions of
+ <application>openssl</application>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Disallow <acronym>GSSAPI</acronym> authentication on local connections,
+ since it requires a hostname to function correctly (Magnus)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <application>ecpg</application> report the proper SQLSTATE if the connection
+ disappears (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>psql</application>'s <literal>numericlocale</literal> option to not
+ format strings it shouldn't in latex and troff output formats (Heikki)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <application>psql</application> return the correct exit status (3) when
+ <literal>ON_ERROR_STOP</literal> and <literal>--single-transaction</literal> are
+ both specified and an error occurs during the implied <command>COMMIT</command>
+ (Bruce)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix plpgsql failure in one case where a composite column is set to NULL
+ (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible failure when calling PL/Perl functions from PL/PerlU
+ or vice versa (Tim Bunce)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add <literal>volatile</literal> markings in PL/Python to avoid possible
+ compiler-specific misbehavior (Zdenek Kotala)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure PL/Tcl initializes the Tcl interpreter fully (Tom)
+ </para>
+
+ <para>
+ The only known symptom of this oversight is that the Tcl
+ <literal>clock</literal> command misbehaves if using Tcl 8.5 or later.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent crash in <filename>contrib/dblink</filename> when too many key
+ columns are specified to a <function>dblink_build_sql_*</function> function
+ (Rushabh Lathia, Joe Conway)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Allow zero-dimensional arrays in <filename>contrib/ltree</filename> operations
+ (Tom)
+ </para>
+
+ <para>
+ This case was formerly rejected as an error, but it's more convenient to
+ treat it the same as a zero-element array. In particular this avoids
+ unnecessary failures when an <type>ltree</type> operation is applied to the
+ result of <literal>ARRAY(SELECT ...)</literal> and the sub-select returns no
+ rows.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix assorted crashes in <filename>contrib/xml2</filename> caused by sloppy
+ memory management (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make building of <filename>contrib/xml2</filename> more robust on Windows
+ (Andrew)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix race condition in Windows signal handling (Radu Ilie)
+ </para>
+
+ <para>
+ One known symptom of this bug is that rows in <structname>pg_listener</structname>
+ could be dropped under heavy load.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2010e
+ for DST law changes in Bangladesh, Chile, Fiji, Mexico, Paraguay, Samoa.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-3-9">
<title>Release 8.3.9</title>
Modified: traduc/branches/bv83x/version.xml
===================================================================
--- traduc/branches/bv83x/version.xml 2010-03-13 15:01:57 UTC (rev 1477)
+++ traduc/branches/bv83x/version.xml 2010-03-13 15:10:56 UTC (rev 1478)
@@ -1,2 +1,2 @@
-<!ENTITY version "8.3.9">
+<!ENTITY version "8.3.10">
<!ENTITY majorversion "8.3">
Plus d'informations sur la liste de diffusion Trad