Mise à jour en version 8.4.10

backup.xml

@@ -1475,7 +1475,7 @@ tar -rf /var/lib/pgsql/backup.tar /var/lib/pgsql/archive/
       des scripts pour définir leur <varname>archive_command</varname>, de
       sorte que leur <filename>postgresql.conf</filename> semble très simple&nbsp;:
 <programlisting>
-archive_command = 'local_backup_script.sh'
+archive_command = 'local_backup_script.sh "%p" "%f"'
 </programlisting>
       Utiliser un script séparé est conseillé à chaque fois qu'il est envisagé
       d'utiliser plusieurs commandes pour le processus d'archivage.

catalogs.xml

@@ -6356,9 +6356,6 @@ grand-chose -->
       <entry>
        L'OID de l'objet dans son catalogue système ou NULL si l'objet n'est
        pas un objet général de la base de données.
-       Pour les verrous informatifs, il est utilisé pour distinguer
-       les deux espaces de clé (<literal>1</literal> pour une clé int8,
-       <literal>2</literal> pour deux clés int4).
       </entry>
      </row>
      <row>

client-auth.xml

@@ -1254,7 +1254,9 @@ omicron       bryanh            guest1
       <term><literal>ldapserver</literal></term>
       <listitem>
        <para>
-        Nom ou adresse IP du serveur LDAP auquel se connecter.
+        Noms ou adresses IP des serveurs LDAP auxquels se connecter.
+        Plusieurs serveurs peuvent être indiqués, en les séparant par
+        des espaces.
        </para>
       </listitem>
      </varlistentry>

config.xml

@@ -5675,16 +5675,7 @@ plruby.use_strict = true        # generates error, unknown class name</programli
        <para>
         Si activé, génère des informations à propos de l'utilisation de verrous
         utilisateurs. La sortie est la même que pour <symbol>trace_locks</symbol>,
-        mais restreinte aux verrous utilisateurs.
-       </para>
-       <para>
-        Les verrous utilisateurs ont été supprimés depuis PostgreSQL version 8.2.
-        Cette option n'a aucun effet maintenant.
-       </para>
-       <para>
-        Ce paramètre n'est disponible que si la macro <symbol>LOCK_DEBUG</symbol>
-        a été définie quand <productname>PostgreSQL</productname> a été
-        compilé.
+        mais restreinte aux verrous informatifs.
        </para>
       </listitem>
      </varlistentry>

libpq.xml

@@ -311,7 +311,10 @@
 
              <row>
               <entry><literal>require</literal></entry>
-              <entry>essaie seulement une connexion <acronym>SSL</acronym></entry>
+              <entry>essaie seulement une connexion <acronym>SSL</acronym>.
+                Si un certificat racine d'autorité est présent, vérifie
+                le certificat de la même façon que si
+                <literal>verify-ca</literal> était spécifié</entry>
              </row>
 
              <row>
@@ -5664,6 +5667,19 @@ ldap://ldap.masociété.com/dc=masociété,dc=com?uniqueMember?one?(cn=mabase)
    <envar>PGSSLROOTCERT</envar> et <envar>PGSSLCRL</envar>.
   </para>
 
+  <note>
+   <para>
+    Pour une compatibilité ascendantes avec les anciennes versions de
+    PostgreSQL, si un certificat racine d'autorité existe, le comportement
+    de <literal>sslmode</literal>=<literal>require</literal> sera identique
+    à celui de <literal>verify-ca</literal>. Cela signifie que le
+    certificat du serveur est validé par l'autorité de certificat. Il ne
+    faut pas se baser sur ce comportement. Les applications qui ont besoin
+    d'une validation du certificat doivent toujours utiliser
+    <literal>validate-ca</literal> ou <literal>validate-full</literal>.
+   </para>
+  </note>
+
  </sect2>
 
  <sect2 id="libpq-ssl-clientcert">
@@ -6074,8 +6090,13 @@ commandes concurrentes, utilisez plusieurs connexions).
 </para>
 
 <para>
-Les objets <structname>PGresult</structname> sont en lecture seule après leur création
-et, du coup, ils peuvent être passés librement entre les threads.
+Les objets <structname>PGresult</structname> sont généralement en lecture
+seule après leur création et, du coup, ils peuvent être passés librement
+entre les threads. Néanmoins, si vous utilisez une des fonctions de
+modification de <structname>PGresult</structname> décrites dans <xref
+linkend="libpq-misc"/> ou <xref linkend="libpq-events"/>, c'est à vous
+d'éviter les opérations parallèles sur le même <structname>PGresult</structname>,
++   too.
 </para>
 
 <para>

ref/psql-ref.xml

@@ -1976,10 +1976,11 @@ lo_import 152801
 
 
       <varlistentry>
-        <term><literal>\q</literal></term>
+        <term><literal>\q</literal> ou <literal>\quit</literal></term>
         <listitem>
         <para>
         Quitte le programme <application>psql</application>.
+        Avec un script, seule l'exécution du script est terminée.
         </para>
         </listitem>
       </varlistentry>

release-8.2.xml

@@ -4,6 +4,234 @@
      par      $Author: gleu $
      révision $Revision: 1317 $ -->
 
+ <sect1 id="release-8-2-23">
+  <title>Release 8.2.23</title>
+
+  <note>
+  <title>Release Date</title>
+  <simpara>2011-12-05</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 8.2.22.
+   For information about new features in the 8.2 major release, see
+   <xref linkend="release-8-2"/>.
+  </para>
+
+  <para>
+   This is expected to be the last <productname>PostgreSQL</productname> release
+   in the 8.2.X series.  Users are encouraged to update to a newer
+   release branch soon.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 8.2.23</title>
+
+   <para>
+    A dump/restore is not required for those running 8.2.X.
+   </para>
+
+   <para>
+    However, a longstanding error was discovered in the definition of the
+    <literal>information_schema.referential_constraints</literal> view.  If you
+    rely on correct results from that view, you should replace its
+    definition as explained in the first changelog item below.
+   </para>
+
+   <para>
+    Also, 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>
+      Fix bugs in <literal>information_schema.referential_constraints</literal> view
+      (Tom Lane)
+     </para>
+
+     <para>
+      This view was being insufficiently careful about matching the
+      foreign-key constraint to the depended-on primary or unique key
+      constraint.  That could result in failure to show a foreign key
+      constraint at all, or showing it multiple times, or claiming that it
+      depends on a different constraint than the one it really does.
+     </para>
+
+     <para>
+      Since the view definition is installed by <application>initdb</application>,
+      merely upgrading will not fix the problem.  If you need to fix this
+      in an existing installation, you can (as a superuser) drop the
+      <literal>information_schema</literal> schema then re-create it by sourcing
+      <filename><replaceable>SHAREDIR</replaceable>/information_schema.sql</filename>.
+      (Run <literal>pg_config --sharedir</literal> if you're uncertain where
+      <replaceable>SHAREDIR</replaceable> is.)  This must be repeated in each database
+      to be fixed.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Fix TOAST-related data corruption during <literal>CREATE TABLE dest AS
+      SELECT * FROM src</literal> or <literal>INSERT INTO dest SELECT * FROM src</literal>
+      (Tom Lane)
+     </para>
+
+     <para>
+      If a table has been modified by <command>ALTER TABLE ADD COLUMN</command>,
+      attempts to copy its data verbatim to another table could produce
+      corrupt results in certain corner cases.
+      The problem can only manifest in this precise form in 8.4 and later,
+      but we patched earlier versions as well in case there are other code
+      paths that could trigger the same bug.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Fix race condition during toast table access from stale syscache entries
+      (Tom Lane)
+     </para>
+
+     <para>
+      The typical symptom was transient errors like <quote>missing chunk
+      number 0 for toast value NNNNN in pg_toast_2619</quote>, where the cited
+      toast table would always belong to a system catalog.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Improve locale support in <type>money</type> type's input and output
+      (Tom Lane)
+     </para>
+
+     <para>
+      Aside from not supporting all standard
+      <link linkend="guc-lc-monetary"><varname>lc_monetary</varname></link>
+      formatting options, the input and output functions were inconsistent,
+      meaning there were locales in which dumped <type>money</type> values could
+      not be re-read.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Don't let <link
+      linkend="guc-transform-null-equals"><varname>transform_null_equals</varname></link>
+      affect <literal>CASE foo WHEN NULL ...</literal> constructs
+      (Heikki Linnakangas)
+     </para>
+
+     <para>
+      <varname>transform_null_equals</varname> is only supposed to affect
+      <literal>foo = NULL</literal> expressions written directly by the user, not
+      equality checks generated internally by this form of <literal>CASE</literal>.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Change foreign-key trigger creation order to better support
+      self-referential foreign keys (Tom Lane)
+     </para>
+
+     <para>
+      For a cascading foreign key that references its own table, a row update
+      will fire both the <literal>ON UPDATE</literal> trigger and the
+      <literal>CHECK</literal> trigger as one event.  The <literal>ON UPDATE</literal>
+      trigger must execute first, else the <literal>CHECK</literal> will check a
+      non-final state of the row and possibly throw an inappropriate error.
+      However, the firing order of these triggers is determined by their
+      names, which generally sort in creation order since the triggers have
+      auto-generated names following the convention
+      <quote>RI_ConstraintTrigger_NNNN</quote>.  A proper fix would require
+      modifying that convention, which we will do in 9.2, but it seems risky
+      to change it in existing releases.  So this patch just changes the
+      creation order of the triggers.  Users encountering this type of error
+      should drop and re-create the foreign key constraint to get its
+      triggers into the right order.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Preserve blank lines within commands in <application>psql</application>'s command
+      history (Robert Haas)
+     </para>
+
+     <para>
+      The former behavior could cause problems if an empty line was removed
+      from within a string literal, for example.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Use the preferred version of <application>xsubpp</application> to build PL/Perl,
+      not necessarily the operating system's main copy
+      (David Wheeler and Alex Hunsaker)
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Honor query cancel interrupts promptly in <function>pgstatindex()</function>
+      (Robert Haas)
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Ensure VPATH builds properly install all server header files
+      (Peter Eisentraut)
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Shorten file names reported in verbose error messages (Peter Eisentraut)
+     </para>
+
+     <para>
+      Regular builds have always reported just the name of the C file
+      containing the error message call, but VPATH builds formerly
+      reported an absolute path name.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Fix interpretation of Windows timezone names for Central America
+      (Tom Lane)
+     </para>
+
+     <para>
+      Map <quote>Central America Standard Time</quote> to <literal>CST6</literal>, not
+      <literal>CST6CDT</literal>, because DST is generally not observed anywhere in
+      Central America.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Update time zone data files to <application>tzdata</application> release 2011n
+      for DST law changes in Brazil, Cuba, Fiji, Palestine, Russia, and Samoa;
+      also historical corrections for Alaska and British East Africa.
+     </para>
+    </listitem>
+
+   </itemizedlist>
+
+  </sect2>
+ </sect1>
+
  <sect1 id="release-8-2-22">
   <title>Release 8.2.22</title>