[Trad] [svn:pgfr] r1480 - in traduc/trunk/postgresql: . ref
admin at listes.postgresql.fr
admin at listes.postgresql.fr
Sam 13 Mar 16:46:36 CET 2010
Author: gleu
Date: 2010-03-13 16:46:36 +0100 (Sat, 13 Mar 2010)
New Revision: 1480
Modified:
traduc/trunk/postgresql/config.xml
traduc/trunk/postgresql/installation.xml
traduc/trunk/postgresql/keywords.xml
traduc/trunk/postgresql/mvcc.xml
traduc/trunk/postgresql/plperl.xml
traduc/trunk/postgresql/plpgsql.xml
traduc/trunk/postgresql/ref/create_foreign_data_wrapper.xml
traduc/trunk/postgresql/ref/create_function.xml
traduc/trunk/postgresql/ref/psql-ref.xml
traduc/trunk/postgresql/release-7.4.xml
traduc/trunk/postgresql/release-8.0.xml
traduc/trunk/postgresql/release-8.1.xml
traduc/trunk/postgresql/release-8.2.xml
traduc/trunk/postgresql/release-8.3.xml
traduc/trunk/postgresql/release-8.4.xml
traduc/trunk/postgresql/version.xml
Log:
Mise ?\195?\160 jour en version 8.4.3.
Modified: traduc/trunk/postgresql/config.xml
===================================================================
--- traduc/trunk/postgresql/config.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/config.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -623,6 +623,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/trunk/postgresql/installation.xml
===================================================================
--- traduc/trunk/postgresql/installation.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/installation.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -2394,7 +2394,7 @@
<title>Cygwin</title>
<indexterm zone="installation-notes-cygwin">
- <primary>Cyginw</primary>
+ <primary>Cygwin</primary>
<secondary>installation sur</secondary>
</indexterm>
@@ -2654,18 +2654,14 @@
décrit dans ce chapitre ; la compilation via Visual C++ fonctionne de
façon totalement différente et est décrite dans <phrase>la
documentation</phrase><phrase><xref linkend="install-win32"/></phrase>.
- Il y a aussi un binaire précompilé que vous pouvez trouver sur
- <ulink url="http://pgfoundry.org/projects/pginstaller"></ulink>.
C'est une compilation totalement native qui n'utilise aucun logiciel
- supplémentaire comme MinGW. Les fichiers d'installation prêts à l'emploi
- sont disponibles sur les serveurs FTP PostgreSQL principaux, dans le
- répertoire <filename>binary/win32</filename>.
+ supplémentaire comme MinGW. Un installeur est disponible sur le serveur
+ web officiel de PostgreSQL.
</para>
<para>
- Le port natif Win32 requiert un système Microsoft à technologie NT
- 32 bits, comme Windows NT 4, Windows 2000/2003 ou Windows XP. (NT 4
- n'est plus supporté.) Les systèmes plus anciens n'ont pas l'infrastructure
+ Le port natif Windows requiert un système Microsoft 200 ou ultérieurs,
+ 32 bits ou 64 bits. Les systèmes plus anciens n'ont pas l'infrastructure
nécessaire (mais Cygwin peut être utilisé pour ceux-ci). MinGW, le système
de compilation similaire à Unix, et MSYS, une suite d'outils Unix nécessaires
pour exécuter des scripts shell tels que <command>configure</command>, peuvent
Modified: traduc/trunk/postgresql/keywords.xml
===================================================================
--- traduc/trunk/postgresql/keywords.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/keywords.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -3535,7 +3535,7 @@
</row>
<row>
<entry><token>OVER</token></entry>
- <entry></entry>
+ <entry>réservé (peut être une fonction ou un type)</entry>
<entry>réservé</entry>
<entry>réservé</entry>
<entry></entry>
@@ -5575,9 +5575,9 @@
</row>
<row>
<entry><token>WINDOW</token></entry>
- <entry></entry>
<entry>réservé</entry>
<entry>réservé</entry>
+ <entry>réservé</entry>
<entry></entry>
<entry></entry>
</row>
Modified: traduc/trunk/postgresql/mvcc.xml
===================================================================
--- traduc/trunk/postgresql/mvcc.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/mvcc.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -1098,7 +1098,7 @@
SELECT pg_advisory_lock(id) FROM foo WHERE id > 12345 LIMIT 100; -- danger !
SELECT pg_advisory_lock(q.id) FROM
(
- SELECT id FROM foo WHERE id > 12345 LIMIT 100;
+ SELECT id FROM foo WHERE id > 12345 LIMIT 100
) q; -- ok
</screen>
Dans les requêtes ci-dessus, la deuxième forme est dangereuse parce que
Modified: traduc/trunk/postgresql/plperl.xml
===================================================================
--- traduc/trunk/postgresql/plperl.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/plperl.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -311,27 +311,46 @@
<para>
L'accès à la base de données à l'intérieur de vos fonctions écrites en Perl
peut se faire à partir des fonctions suivantes :
+ </para>
<variablelist>
- <varlistentry>
+ <varlistentry>
+ <indexterm>
+ <primary>spi_exec_query</primary>
+ <secondary>in PL/Perl</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>spi_query</primary>
+ <secondary>in PL/Perl</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>spi_fetchrow</primary>
+ <secondary>in PL/Perl</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>spi_prepare</primary>
+ <secondary>in PL/Perl</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>spi_exec_prepared</primary>
+ <secondary>in PL/Perl</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>spi_query_prepared</primary>
+ <secondary>in PL/Perl</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>spi_cursor_close</primary>
+ <secondary>in PL/Perl</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>spi_freeplan</primary>
+ <secondary>in PL/Perl</secondary>
+ </indexterm>
- <term><literal><function>spi_exec_query</function>(<replaceable>query</replaceable> [, <replaceable>max-rows</replaceable>])</literal></term>
- <term><literal><function>spi_query</function>(<replaceable>command</replaceable>)</literal></term>
- <term><literal><function>spi_fetchrow</function>(<replaceable>cursor</replaceable>)</literal></term>
- <term><literal><function>spi_prepare</function>(<replaceable>command</replaceable>, <replaceable>argument types</replaceable>)</literal></term>
- <term><literal><function>spi_exec_prepared</function>(<replaceable>plan</replaceable>)</literal></term>
- <term><literal><function>spi_query_prepared</function>(<replaceable>plan</replaceable> [, <replaceable>attributes</replaceable>], <replaceable>arguments</replaceable>)</literal></term>
- <term><literal><function>spi_cursor_close</function>(<replaceable>cursor</replaceable>)</literal></term>
- <term><literal><function>spi_freeplan</function>(<replaceable>plan</replaceable>)</literal></term>
-
-
- <listitem>
- <indexterm>
- <primary>spi_exec_query</primary>
- <secondary>en PL/Perl</secondary>
- </indexterm>
-
- <para>
+ <term><literal><function>spi_exec_query</>(<replaceable>query</replaceable> [, <replaceable>max-rows</replaceable>])</literal></term>
+ <listitem>
+ <para>
<literal>spi_exec_query</literal> exécute une commande SQL et renvoie
l'ensemble complet de la ligne comme une référence à un table de
références hachées. <emphasis>Vous ne devez utiliser cette commande
@@ -389,6 +408,15 @@
SELECT * FROM test_munge();
</programlisting>
</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal><function>spi_query</>(<replaceable>command</replaceable>)</literal></term>
+ <term><literal><function>spi_fetchrow</>(<replaceable>cursor</replaceable>)</literal></term>
+ <term><literal><function>spi_cursor_close</>(<replaceable>cursor</replaceable>)</literal></term>
+
+ <listitem>
<para>
<literal>spi_query</literal> et <literal>spi_fetchrow</literal>
fonctionnent ensemble comme une paire d'ensembles de lignes pouvant être
@@ -427,38 +455,69 @@
</para>
<para>
+ Habituellement, <function>spi_fetchrow</function> devra être répété jusqu'à
+ ce qu'il renvoie <literal>undef</literal>, indiquant qu'il n'y a plus de
+ lignes à lire. Le curseur renvoyé par <literal>spi_query</literal> est
+ automatiquement libéré quand
+ <function>spi_fetchrow</function> renvoie <literal>undef</literal>. Si vous
+ ne souhaitez pas lire toutes les lignes, appelez à la place
+ <function>spi_cursor_close</function> pour libérer le curseur. Un échec ici
+ résultera en des pertes mémoire.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal><function>spi_prepare</>(<replaceable>command</replaceable>, <replaceable>argument types</replaceable>)</literal></term>
+ <term><literal><function>spi_query_prepared</>(<replaceable>plan</replaceable>, <replaceable>arguments</replaceable>)</literal></term>
+ <term><literal><function>spi_exec_prepared</>(<replaceable>plan</replaceable> [, <replaceable>attributes</replaceable>], <replaceable>arguments</replaceable>)</literal></term>
+ <term><literal><function>spi_freeplan</>(<replaceable>plan</replaceable>)</literal></term>
+
+ <listitem>
+ <para>
<literal>spi_prepare</literal>, <literal>spi_query_prepared</literal>,
<literal>spi_exec_prepared</literal> et <literal>spi_freeplan</literal>
- implémentent la même fonctionnalité mais pour les requêtes préparées. Une
- fois que le plan de requêtes est préparé par un appel à
+ implémentent la même fonctionnalité, mais pour des requêtes préparées.
+ <literal>spi_prepare</literal> accepte une chaîne pour la requête avec des
+ arguments numérotés ($1, $2, etc) et une liste de chaînes indiquant le type
+ des arguments :
+<programlisting>
+$plan = spi_prepare('SELECT * FROM test WHERE id > $1 AND name = $2', 'INTEGER', 'TEXT');
+</programlisting>
+ Une fois qu'un plan est préparé suite à un appel à
<literal>spi_prepare</literal>, le plan peut être utilisé à la place de la
requête, soit dans <literal>spi_exec_prepared</literal>, où le résultat est
- identique à celui renvoyé par <literal>spi_exec_query</literal>, soit
- <literal>spi_query_prepared</literal> qui renvoie un curseur exactement comme
- le fait <literal>spi_query</literal>, qui pourra être passé par la suite à
- <literal>spi_fetchrow</literal>.
+ identique à celui renvoyé par <literal>spi_exec_query</literal>, soit dans
+ <literal>spi_query_prepared</literal> qui renvoit un curseur exactement comme
+ le fait <literal>spi_query</literal>, qui peut ensuite être passé à
+ <literal>spi_fetchrow</literal>. Le deuxième paramètre, optionnel, de
+ <literal>spi_exec_prepared</literal> est une référence hachée des
+ attributs ; le seul attribut actuellement supporté est
+ <literal>limit</literal>, qui configure le nombre maximum de lignes renvoyées
+ par une requête.
</para>
<para>
- L'avantage des requêtes préparées est qu'il est possible d'utiliser un plan
- préparé pour plus d'une exécution de requête. Une fois le plan inutile, il
- pourra être libéré avec <literal>spi_freeplan</literal> :
+ L'avantage des requêtes préparées est que cela rend possible l'utilisation
+ d'un plan préparé par plusieurs exécutions de la requête. Une fois que le
+ plan n'est plus utile, il peut être libéré avec
+ <literal>spi_freeplan</literal> :
</para>
<para>
<programlisting>
-CREATE OR REPLACE FUNCTION init() RETURNS INTEGER AS $$
+CREATE OR REPLACE FUNCTION init() RETURNS VOID AS $$
$_SHARED{my_plan} = spi_prepare( 'SELECT (now() + $1)::date AS now', 'INTERVAL');
$$ LANGUAGE plperl;
CREATE OR REPLACE FUNCTION add_time( INTERVAL ) RETURNS TEXT AS $$
- return spi_exec_prepared(
+ return spi_exec_prepared(
$_SHARED{my_plan},
- $_[0],
+ $_[0]
)->{rows}->[0]->{now};
$$ LANGUAGE plperl;
-CREATE OR REPLACE FUNCTION done() RETURNS INTEGER AS $$
+CREATE OR REPLACE FUNCTION done() RETURNS VOID AS $$
spi_freeplan( $_SHARED{my_plan});
undef $_SHARED{my_plan};
$$ LANGUAGE plperl;
@@ -467,29 +526,56 @@
SELECT add_time('1 day'), add_time('2 days'), add_time('3 days');
SELECT done();
- add_time | add_time | add_time
+ add_time | add_time | add_time
------------+------------+------------
2005-12-10 | 2005-12-11 | 2005-12-12
</programlisting>
</para>
<para>
- Notez que les indices des paramètres dans <literal>spi_prepare</literal>
- sont définis via $1, $2, $3, etc, pour éviter de déclarer des chaînes de
- requête entre guillemets doubles, ce qui pourrait amener à des bogues
- difficilement supprimables.
+ Notez que l'indice du paramètre dans <literal>spi_prepare</literal> est
+ défini via $1, $2, $3, etc, donc évitez de déclarer des chaînes de requêtes
+ qui pourraient aisément amener des bogues difficiles à trouver et corriger.
</para>
<para>
- Habituellement, <function>spi_fetchrow</function> devra être répété jusqu'à
- ce qu'il renvoie <literal>undef</literal>, indiquant qu'il n'y a plus de
- lignes à lire. Le curseur est automatiquement libéré quand
- <function>spi_fetchrow</function> renvoie <literal>undef</literal>. Si vous
- ne souhaitez pas lire toutes les lignes, appelez à la place
- <function>spi_cursor_close</function> pour libérer le curseur. Un échec ici
- résultera en des pertes mémoire.
+ Cet autre exemple illustre l'utilisation d'un paramètre optionnel avec
+ <literal>spi_exec_prepared</literal> :
</para>
- </listitem>
+
+ <para>
+ <programlisting>
+CREATE TABLE hosts AS SELECT id, ('192.168.1.'||id)::inet AS address FROM generate_series(1,3) AS id;
+
+CREATE OR REPLACE FUNCTION init_hosts_query() RETURNS VOID AS $$
+ $_SHARED{plan} = spi_prepare('SELECT * FROM hosts WHERE address << $1', 'inet');
+$$ LANGUAGE plperl;
+
+CREATE OR REPLACE FUNCTION query_hosts(inet) RETURNS SETOF hosts AS $$
+ return spi_exec_prepared(
+ $_SHARED{plan},
+ {limit => 2},
+ $_[0]
+ )->{rows};
+$$ LANGUAGE plperl;
+
+CREATE OR REPLACE FUNCTION release_hosts_query() RETURNS VOID AS $$
+ spi_freeplan($_SHARED{plan});
+ undef $_SHARED{plan};
+$$ LANGUAGE plperl;
+
+SELECT init_hosts_query();
+SELECT query_hosts('192.168.1.0/30');
+SELECT release_hosts_query();
+
+ query_hosts
+-----------------
+ (1,192.168.1.1)
+ (2,192.168.1.2)
+(2 rows)
+ </programlisting>
+ </para>
+ </listitem>
</varlistentry>
<varlistentry>
@@ -521,7 +607,6 @@
</listitem>
</varlistentry>
</variablelist>
- </para>
</sect1>
<sect1 id="plperl-data">
Modified: traduc/trunk/postgresql/plpgsql.xml
===================================================================
--- traduc/trunk/postgresql/plpgsql.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/plpgsql.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -3998,23 +3998,6 @@
<itemizedlist>
<listitem>
<para>
- Vous ne pouvez pas utiliser des noms de paramètres identiques aux
- colonnes qui sont référencées dans la fonction. Oracle vous permet de le
- faire si vous qualifiez le nom du paramètre en utilisant
- <literal>nom_fonction.nom_paramètre</literal>.
- Dans <application>PL/pgSQL</application>, vous pouvez éviter un conflit
- en qualifiant le nom de colonne ou de table.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Il n'y a pas de valeurs par défaut pour les paramètres dans <productname>PostgreSQL</productname>.
- </para>
- </listitem>
-
- <listitem>
- <para>
Si un nom utilisé dans une commande SQL peut être soit un nom de colonne
d'une table soit une référence à une variable de la fonction,
<application>PL/SQL</application> le traite comme un nom de commande
Modified: traduc/trunk/postgresql/ref/create_foreign_data_wrapper.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_foreign_data_wrapper.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/ref/create_foreign_data_wrapper.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -78,10 +78,9 @@
validation doit prendre deux arguments : l'un du type
<type>text[]</type>, qui contiendra le tableau d'options, tel qu'il est
stocké dans les catalogues systèmes, et l'autre de type <type>oid</type>,
- qui sera l'OID du catalogue système contenant les options, ou zéro si le
- contexte est inconnu. Le type de retour est inconnu ; la fonction
- devrait indiquer les options invalides grâce à la fonction
- <function>ereport()</function>.
+ qui sera l'OID du catalogue système contenant les options. Le type de
+ retour est inconnu ; la fonction devrait indiquer les options
+ invalides grâce à la fonction <function>ereport()</function>.
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/ref/create_function.xml
===================================================================
--- traduc/trunk/postgresql/ref/create_function.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/ref/create_function.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -570,6 +570,13 @@
remplacer (cela inclut aussi les membres du rôle propriétaire).
</para>
+ <para>
+ Si une fonction est déclarée <literal>STRICT</> avec un argument
+ <literal>VARIADIC</>, la vérification du côté strict d'une fonction teste
+ si le tableau variadic <emphasis>lui-même</> est non NULL. La fonction sera
+ quand même appelée si le tableau contient des éléments NULL.
+ </para>
+
</refsect1>
<refsect1 id="sql-createfunction-examples">
Modified: traduc/trunk/postgresql/ref/psql-ref.xml
===================================================================
--- traduc/trunk/postgresql/ref/psql-ref.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/ref/psql-ref.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -757,7 +757,7 @@
<tip>
<para>
Pour afficher votre répertoire courant, utilisez
- <literal>\!pwd</literal>.
+ <literal>\! pwd</literal>.
</para>
</tip>
</listitem>
Modified: traduc/trunk/postgresql/release-7.4.xml
===================================================================
--- traduc/trunk/postgresql/release-7.4.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/release-7.4.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -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/trunk/postgresql/release-8.0.xml
===================================================================
--- traduc/trunk/postgresql/release-8.0.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/release-8.0.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -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/trunk/postgresql/release-8.1.xml
===================================================================
--- traduc/trunk/postgresql/release-8.1.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/release-8.1.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -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/trunk/postgresql/release-8.2.xml
===================================================================
--- traduc/trunk/postgresql/release-8.2.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/release-8.2.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -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/trunk/postgresql/release-8.3.xml
===================================================================
--- traduc/trunk/postgresql/release-8.3.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/release-8.3.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -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/trunk/postgresql/release-8.4.xml
===================================================================
--- traduc/trunk/postgresql/release-8.4.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/release-8.4.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -4,6 +4,473 @@
par $Author: gleu $
révision $Revision: 1317 $ -->
+ <sect1 id="release-8-4-3">
+ <title>Release 8.4.3</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2010-03-15</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.4.2.
+ For information about new features in the 8.4 major release, see
+ <xref linkend="release-8-4"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 8.4.3</title>
+
+ <para>
+ A dump/restore is not required for those running 8.4.X.
+ However, if you are upgrading from a version earlier than 8.4.2,
+ see the release notes for 8.4.2.
+ </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 crash due to overenthusiastic invalidation of cached
+ plan for <command>ROLLBACK</command> (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>
+ Fix bug in WAL redo cleanup method for GIN indexes (Heikki)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect comparison of scan key in GIN index search (Teodor)
+ </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 bug occurring when trying to inline a SQL function that returns
+ a set of a composite type that contains dropped columns (Tom)
+ </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>
+ Avoid failure when <command>EXPLAIN</command> has to print a FieldStore or
+ assignment ArrayRef expression (Tom)
+ </para>
+
+ <para>
+ These cases can arise now that <command>EXPLAIN VERBOSE</command> tries to
+ print plan node target lists.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid an unnecessary coercion failure in some cases where an undecorated
+ literal string appears in a subquery within
+ <command>UNION</command>/<command>INTERSECT</command>/<command>EXCEPT</command> (Tom)
+ </para>
+
+ <para>
+ This fixes a regression for some cases that worked before 8.4.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid undesirable rowtype compatibility check failures in some cases
+ where a whole-row Var has a rowtype that contains dropped columns (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>
+ Always pass the catalog ID to an option validator function specified in
+ <command>CREATE FOREIGN DATA WRAPPER</command> (Martin Pihlak)
+ </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>
+ Add support for doing <literal>FULL JOIN ON FALSE</literal> (Tom)
+ </para>
+
+ <para>
+ This prevents a regression from pre-8.4 releases for some queries that
+ can now be simplified to a constant-false join condition.
+ </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>
+ Prevent treating an <literal>INOUT</literal> cast as representing binary
+ compatibility (Heikki)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Include column name in the message when warning about inability to
+ grant or revoke column-level privileges (Stephen Frost)
+ </para>
+
+ <para>
+ This is more useful than before and helps to prevent confusion when
+ a <command>REVOKE</command> generates multiple messages, which formerly
+ appeared to be duplicates.
+ </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>
+ Protect <application>ecpg</application> against applications freeing strings
+ unexpectedly (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <application>ecpg</application> report the proper SQLSTATE if the connection
+ disappears (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix translation of cell contents in <application>psql</application> <literal>\d</literal>
+ output (Heikki)
+ </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 a small per-query memory leak in <application>psql</application> (Tom)
+ </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 <application>pg_dump</application>'s output of permissions for foreign servers
+ (Heikki)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crash in parallel <application>pg_restore</application> due to
+ out-of-range dependency IDs (Tom)
+ </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 <function>ExecutorEnd</function> from being run on portals created
+ within a failed transaction or subtransaction (Tom)
+ </para>
+
+ <para>
+ This is known to cause issues when using
+ <filename>contrib/auto_explain</filename>.
+ </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>
+ Make the configure script report failure if the C compiler does
+ not provide a working 64-bit integer datatype (Tom)
+ </para>
+
+ <para>
+ This case has been broken for some time, and no longer seems worth
+ supporting, so just reject it at configure time instead.
+ </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-4-2">
<title>Release 8.4.2</title>
Modified: traduc/trunk/postgresql/version.xml
===================================================================
--- traduc/trunk/postgresql/version.xml 2010-03-13 15:13:48 UTC (rev 1479)
+++ traduc/trunk/postgresql/version.xml 2010-03-13 15:46:36 UTC (rev 1480)
@@ -1,2 +1,2 @@
-<!ENTITY version "8.4.2">
+<!ENTITY version "8.4.3">
<!ENTITY majorversion "8.4">
Plus d'informations sur la liste de diffusion Trad