[Trad] [svn:pgfr] r1150 - in traduc/trunk/postgresql: . ref
admin at listes.postgresql.fr
admin at listes.postgresql.fr
Dim 21 Sep 18:25:36 CEST 2008
Author: gleu
Date: 2008-09-21 18:25:36 +0200 (Sun, 21 Sep 2008)
New Revision: 1150
Modified:
traduc/trunk/postgresql/backup.xml
traduc/trunk/postgresql/config.xml
traduc/trunk/postgresql/func.xml
traduc/trunk/postgresql/gin.xml
traduc/trunk/postgresql/install-win32.xml
traduc/trunk/postgresql/ref/pg_dump.xml
traduc/trunk/postgresql/release.xml
Log:
Mise ?\195?\160 jour en version 8.3.4.
Modified: traduc/trunk/postgresql/backup.xml
===================================================================
--- traduc/trunk/postgresql/backup.xml 2008-09-21 15:54:06 UTC (rev 1149)
+++ traduc/trunk/postgresql/backup.xml 2008-09-21 16:25:36 UTC (rev 1150)
@@ -1171,7 +1171,7 @@
doit renvoyer une valeur différente de zéro dans ce cas.
Exemples :
<programlisting>restore_command = 'cp /mnt/serveur/reparchives/%f "%p"'
-restore_command = 'copy /mnt/serveur/reparchives/%f "%p"' # Windows</programlisting>
+restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows</programlisting>
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/config.xml
===================================================================
--- traduc/trunk/postgresql/config.xml 2008-09-21 15:54:06 UTC (rev 1149)
+++ traduc/trunk/postgresql/config.xml 2008-09-21 16:25:36 UTC (rev 1150)
@@ -1837,7 +1837,7 @@
Il est important que la commande ne renvoie un code de sortie nul
que si, et seulement si, elle réussit. Exemples :
<programlisting>archive_command = 'cp "%p" /mnt/server/archivedir/"%f"'
-archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows</programlisting>
+archive_command = 'copy "%p" "C:\\server\\archivedir\\%f"' # Windows</programlisting>
</para>
</listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/func.xml
===================================================================
--- traduc/trunk/postgresql/func.xml 2008-09-21 15:54:06 UTC (rev 1149)
+++ traduc/trunk/postgresql/func.xml 2008-09-21 16:25:36 UTC (rev 1150)
@@ -8610,6 +8610,58 @@
</sect3>
<sect3>
+ <title><literal>xmlagg</literal></title>
+
+ <indexterm>
+ <primary>xmlagg</primary>
+ </indexterm>
+
+<synopsis>
+<function>xmlagg</function>(<replaceable>xml</replaceable>)
+</synopsis>
+
+ <para>
+ La fonction <function>xmlagg</function> est, comme les autres fonctions
+ ci-dessous, une fonction d'agrégat. Elle concatène les valeurs en entrée
+ de l'appel de la fonction, comme <function>xmlconcat</function> le fait.
+ Voir <xref linkend="functions-aggregate"/> pour plus d'informations sur
+ les fonctions d'agrégat.
+ </para>
+
+ <para>
+ Exemple :
+<screen><![CDATA[
+CREATE TABLE test (y int, x xml);
+INSERT INTO test VALUES (1, '<foo>abc</foo>');
+INSERT INTO test VALUES (2, '<bar/>');
+SELECT xmlagg(x) FROM test;
+ xmlagg
+----------------------
+ <foo>abc</foo><bar/>
+]]></screen>
+ </para>
+
+ <para>
+ Notez que, dans l'implémentation actuelle, l'ordre de la concaténation
+ n'est en principe pas défini. Néanmoins, cela peut fonctionner en
+ triant préalablement les valeurs en entrée. En reprenant l'exemple
+ ci-dessus, on pourrait influencer l'ordre de cette façon :
+<screen><![CDATA[
+SELECT xmlagg(x) FROM (SELECT * FROM test ORDER BY y DESC) AS tab;
+ xmlagg
+----------------------
+ <bar/><foo>abc</foo>
+]]></screen>
+
+ Mais le fonctionnement de cette approche n'est pas garantie dans toutes
+ les situations et dans toutes les versions de PostgreSQL. Une version
+ future de PostgreSQL pourrait fournir une fonctionnalité supplémentaire
+ pour contrôler l'ordre d'une bonne façon
+ (<literal>xmlagg(expr ORDER BY expr, expr, ...</literal>).
+ </para>
+ </sect3>
+
+ <sect3>
<title>Prédicats XML</title>
<indexterm>
Modified: traduc/trunk/postgresql/gin.xml
===================================================================
--- traduc/trunk/postgresql/gin.xml 2008-09-21 15:54:06 UTC (rev 1149)
+++ traduc/trunk/postgresql/gin.xml 2008-09-21 16:25:36 UTC (rev 1150)
@@ -46,7 +46,7 @@
<productname>PostgreSQL</productname> est principalement l'oeuvre de
Teodor Sigaev et Oleg Bartunov. Plus d'informations sur <acronym>GIN</acronym>
sont disponibles sur leur <ulink
- url="http://www.sai.msu.su/~megera/oddmuse/index.cgi/Gin">site web</ulink>.
+ url="http://www.sai.msu.su/~megera/wiki/Gin">site web</ulink>.
</para>
</sect1>
Modified: traduc/trunk/postgresql/install-win32.xml
===================================================================
--- traduc/trunk/postgresql/install-win32.xml 2008-09-21 15:54:06 UTC (rev 1149)
+++ traduc/trunk/postgresql/install-win32.xml 2008-09-21 16:25:36 UTC (rev 1150)
@@ -92,14 +92,18 @@
ActiveState Perl est requis pour exécuter les scripts de construction.
Le Perl de MinGW et de Cygwin ne fonctionnera pas. Il doit aussi être
présent dans le PATH. Les binaires de cet outil sont téléchargeables
- à partir de <ulink url="http://www.activestate.com"></ulink>.
+ à partir de <ulink url="http://www.activestate.com"></ulink> (Note :
+ la version 5.8 est requise, la distribution standard libre est
+ suffisante).
</para></listitem>
</varlistentry>
<varlistentry>
<term><productname>ActiveState TCL</productname></term>
<listitem><para>
- Requis pour construire <application>PL/TCL</application>.
+ Requis pour construire <application>PL/TCL</application> (Note :
+ la version 8.4 est requise, la distribution standard libre est
+ suffisante).
</para></listitem>
</varlistentry>
Modified: traduc/trunk/postgresql/ref/pg_dump.xml
===================================================================
--- traduc/trunk/postgresql/ref/pg_dump.xml 2008-09-21 15:54:06 UTC (rev 1149)
+++ traduc/trunk/postgresql/ref/pg_dump.xml 2008-09-21 16:25:36 UTC (rev 1150)
@@ -610,8 +610,15 @@
<term><option>--compress=<replaceable class="parameter">0..9</replaceable></option></term>
<listitem>
<para>
- Le niveau de compression, si le format d'archive la supporte.
- Actuellement, seul le format personnalisé supporte la compression.
+ Spécifie le niveau de compression à utiliser. Zéro signifie sans
+ compression. Pour le format d'archive personnalisé, cela signifie la
+ compression des segments individuels des données des tables. La valeur
+ par défaut est de compresser à un niveau modéré. Pour le format texte,
+ indiquer une valeur différente de zéro fait que le fichier entier est
+ compressé, bien qu'il a été envoyé à
+ <application>gzip</application> ; mais par défaut, la sortie n'est
+ pas compressée. Le format d'archive tar ne supporte pas du tout la
+ compression.
</para>
</listitem>
</varlistentry>
@@ -743,22 +750,14 @@
</para>
<para>
- <application>pg_dump</application> souffre quelques limitations :
-
- <itemizedlist>
- <listitem>
- <para>
- Lorsqu'une sauvegarde des seules données est sélectionnée et que l'option
- <option>--disable-triggers</option> est utilisée,
- <application>pg_dump</application> engendre des commandes de désactivation des
- déclencheurs sur les tables utilisateur avant l'insertion des données et des
- commandes de réactivation après l'insertion. Si la
- restauration est interrompue, il se peut que les catalogues systèmes
- conservent cette position.
- </para>
- </listitem>
-
- </itemizedlist>
+ <application>pg_dump</application> a une limitation ; quand une
+ sauvegarde des seules données est sélectionnée et que l'option
+ <option>--disable-triggers</option> est utilisée,
+ <application>pg_dump</application> engendre des commandes de désactivation
+ des déclencheurs sur les tables utilisateur avant l'insertion des données et
+ des commandes de réactivation après l'insertion. Si la restauration est
+ interrompue, il se peut que les catalogues systèmes conservent cette
+ position.
</para>
<para>
@@ -775,7 +774,10 @@
contient pas les statistiques utilisées par l'optimiseur pour la
planification des requêtes. Il est donc conseillé, pour assurer des
performances correctes, de lancer <command>ANALYZE</command> après
- la restauration d'une sauvegarde.
+ la restauration d'une sauvegarde. Le fichier de sauvegarde ne contient pas
+ non plus de commandes <command>ALTER DATABASE ... SET</command> ; ces
+ paramètres sont sauvegardées par <xref linkend="app-pg-dumpall">, avec les
+ utilisateurs et les paramètres globaux à l'installation.
</para>
<para>
Modified: traduc/trunk/postgresql/release.xml
===================================================================
--- traduc/trunk/postgresql/release.xml 2008-09-21 15:54:06 UTC (rev 1149)
+++ traduc/trunk/postgresql/release.xml 2008-09-21 16:25:36 UTC (rev 1150)
@@ -67,6 +67,360 @@
review, so each item is truly a community effort.
</para>
+ <sect1 id="release-8-3-4">
+ <title>Release 8.3.4</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2008-09-22</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.3.3.
+ 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.4</title>
+
+ <para>
+ A dump/restore is not required for those running 8.3.X.
+ However, if you are upgrading from a version earlier than 8.3.1,
+ see the release notes for 8.3.1.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix bug in btree WAL recovery code (Heikki)
+ </para>
+
+ <para>
+ Recovery failed if the WAL ended partway through a page split operation.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix potential use of wrong cutoff XID for HOT page pruning (Alvaro)
+ </para>
+
+ <para>
+ This error created a risk of corruption in system
+ catalogs that are consulted by <command>VACUUM</command>: dead tuple versions
+ might be removed too soon. The impact of this on actual database
+ operations would be minimal, since the system doesn't follow MVCC
+ rules while examining catalogs, but it might result in transiently
+ wrong output from <application>pg_dump</application> or other client programs.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix potential miscalculation of <structfield>datfrozenxid</structfield> (Alvaro)
+ </para>
+
+ <para>
+ This error may explain some recent reports of failure to remove old
+ <structname>pg_clog</structname> data.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect HOT updates after <structname>pg_class</structname> is reindexed
+ (Tom)
+ </para>
+
+ <para>
+ Corruption of <structname>pg_class</structname> could occur if <literal>REINDEX
+ TABLE pg_class</literal> was followed in the same session by an <literal>ALTER
+ TABLE RENAME</literal> or <literal>ALTER TABLE SET SCHEMA</literal> command.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix missed <quote>combo cid</quote> case (Karl Schnaitter)
+ </para>
+
+ <para>
+ This error made rows incorrectly invisible to a transaction in which they
+ had been deleted by multiple subtransactions that all aborted.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent autovacuum from crashing if the table it's currently
+ checking is deleted at just the wrong time (Alvaro)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Widen local lock counters from 32 to 64 bits (Tom)
+ </para>
+
+ <para>
+ This responds to reports that the counters could overflow in
+ sufficiently long transactions, leading to unexpected <quote>lock is
+ already held</quote> errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible duplicate output of tuples during a GiST index scan (Teodor)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Regenerate foreign key checking queries from scratch when either
+ table is modified (Tom)
+ </para>
+
+ <para>
+ Previously, 8.3 would attempt to replan the query, but would work from
+ previously generated query text. This led to failures if a
+ table or column was renamed.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix missed permissions checks when a view contains a simple
+ <literal>UNION ALL</literal> construct (Heikki)
+ </para>
+
+ <para>
+ Permissions for the referenced tables were checked properly, but not
+ permissions for the view itself.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add checks in executor startup to ensure that the tuples produced by an
+ <command>INSERT</command> or <command>UPDATE</command> will match the target table's
+ current rowtype (Tom)
+ </para>
+
+ <para>
+ This situation is believed to be impossible in 8.3, but it can happen in
+ prior releases, so a check seems prudent.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible repeated drops during <command>DROP OWNED</command> (Tom)
+ </para>
+
+ <para>
+ This would typically result in strange errors such as <quote>cache
+ lookup failed for relation NNN</quote>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix several memory leaks in XML operations (Kris Jurka, Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <function>xmlserialize()</function> to raise error properly for
+ unacceptable target data type (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix a couple of places that mis-handled multibyte characters in text
+ search configuration file parsing (Tom)
+ </para>
+
+ <para>
+ Certain characters occurring in configuration files would always cause
+ <quote>invalid byte sequence for encoding</quote> failures.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Provide file name and line number location for all errors reported
+ in text search configuration files (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <literal>AT TIME ZONE</literal> to first try to interpret its timezone
+ argument as a timezone abbreviation, and only try it as a full timezone
+ name if that fails, rather than the other way around as formerly (Tom)
+ </para>
+
+ <para>
+ The timestamp input functions have always resolved ambiguous zone names
+ in this order. Making <literal>AT TIME ZONE</literal> do so as well improves
+ consistency, and fixes a compatibility bug introduced in 8.1:
+ in ambiguous cases we now behave the same as 8.0 and before did,
+ since in the older versions <literal>AT TIME ZONE</literal> accepted
+ <emphasis>only</emphasis> abbreviations.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix datetime input functions to correctly detect integer overflow when
+ running on a 64-bit platform (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent integer overflows during units conversion when displaying a
+ configuration parameter that has units (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve performance of writing very long log messages to syslog (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Allow spaces in the suffix part of an LDAP URL in
+ <filename>pg_hba.conf</filename> (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix bug in backwards scanning of a cursor on a <literal>SELECT DISTINCT
+ ON</literal> query (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner bug that could improperly push down <literal>IS NULL</literal>
+ tests below an outer join (Tom)
+ </para>
+
+ <para>
+ This was triggered by occurrence of <literal>IS NULL</literal> tests for
+ the same relation in all arms of an upper <literal>OR</literal> clause.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner bug with nested sub-select expressions (Tom)
+ </para>
+
+ <para>
+ If the outer sub-select has no direct dependency on the parent query,
+ but the inner one does, the outer value might not get recalculated
+ for new parent query rows.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner to estimate that <literal>GROUP BY</literal> expressions yielding
+ boolean results always result in two groups, regardless of the
+ expressions' contents (Tom)
+ </para>
+
+ <para>
+ This is very substantially more accurate than the regular <literal>GROUP
+ BY</literal> estimate for certain boolean tests like <replaceable>col</replaceable>
+ <literal>IS NULL</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix PL/PgSQL to not fail when a <literal>FOR</literal> loop's target variable
+ is a record containing composite-type fields (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix PL/Tcl to behave correctly with Tcl 8.5, and to be more careful
+ about the encoding of data sent to or from Tcl (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve performance of <function>PQescapeBytea()</function> (Rudolf Leitgeb)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, work around a Microsoft bug by preventing
+ <application>libpq</application> from trying to send more than 64kB per system call
+ (Magnus)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>ecpg</application> to handle variables properly in <command>SET</command>
+ commands (Michael)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve <application>pg_dump</application> and <application>pg_restore</application>'s
+ error reporting after failure to send a SQL command (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>pg_ctl</application> to properly preserve postmaster
+ command-line arguments across a <literal>restart</literal> (Bruce)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix erroneous WAL file cutoff point calculation in
+ <application>pg_standby</application> (Simon)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2008f (for
+ DST law changes in Argentina, Bahamas, Brazil, Mauritius, Morocco,
+ Pakistan, Palestine, and Paraguay)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-3-3">
<title>Release 8.3.3</title>
@@ -3418,6 +3772,238 @@
</sect2>
</sect1>
+ <sect1 id="release-8-2-10">
+ <title>Release 8.2.10</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2008-09-22</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.2.9.
+ 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.10</title>
+
+ <para>
+ A dump/restore is not required for those running 8.2.X.
+ However, if you are upgrading from a version earlier than 8.2.7,
+ see the release notes for 8.2.7.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix bug in btree WAL recovery code (Heikki)
+ </para>
+
+ <para>
+ Recovery failed if the WAL ended partway through a page split operation.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix potential miscalculation of <structfield>datfrozenxid</structfield> (Alvaro)
+ </para>
+
+ <para>
+ This error may explain some recent reports of failure to remove old
+ <structname>pg_clog</structname> data.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Widen local lock counters from 32 to 64 bits (Tom)
+ </para>
+
+ <para>
+ This responds to reports that the counters could overflow in
+ sufficiently long transactions, leading to unexpected <quote>lock is
+ already held</quote> errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible duplicate output of tuples during a GiST index scan (Teodor)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix missed permissions checks when a view contains a simple
+ <literal>UNION ALL</literal> construct (Heikki)
+ </para>
+
+ <para>
+ Permissions for the referenced tables were checked properly, but not
+ permissions for the view itself.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add checks in executor startup to ensure that the tuples produced by an
+ <command>INSERT</command> or <command>UPDATE</command> will match the target table's
+ current rowtype (Tom)
+ </para>
+
+ <para>
+ <command>ALTER COLUMN TYPE</command>, followed by re-use of a previously
+ cached plan, could produce this type of situation. The check protects
+ against data corruption and/or crashes that could ensue.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible repeated drops during <command>DROP OWNED</command> (Tom)
+ </para>
+
+ <para>
+ This would typically result in strange errors such as <quote>cache
+ lookup failed for relation NNN</quote>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <literal>AT TIME ZONE</literal> to first try to interpret its timezone
+ argument as a timezone abbreviation, and only try it as a full timezone
+ name if that fails, rather than the other way around as formerly (Tom)
+ </para>
+
+ <para>
+ The timestamp input functions have always resolved ambiguous zone names
+ in this order. Making <literal>AT TIME ZONE</literal> do so as well improves
+ consistency, and fixes a compatibility bug introduced in 8.1:
+ in ambiguous cases we now behave the same as 8.0 and before did,
+ since in the older versions <literal>AT TIME ZONE</literal> accepted
+ <emphasis>only</emphasis> abbreviations.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix datetime input functions to correctly detect integer overflow when
+ running on a 64-bit platform (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent integer overflows during units conversion when displaying a
+ configuration parameter that has units (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve performance of writing very long log messages to syslog (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Allow spaces in the suffix part of an LDAP URL in
+ <filename>pg_hba.conf</filename> (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix bug in backwards scanning of a cursor on a <literal>SELECT DISTINCT
+ ON</literal> query (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner bug with nested sub-select expressions (Tom)
+ </para>
+
+ <para>
+ If the outer sub-select has no direct dependency on the parent query,
+ but the inner one does, the outer value might not get recalculated
+ for new parent query rows.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner to estimate that <literal>GROUP BY</literal> expressions yielding
+ boolean results always result in two groups, regardless of the
+ expressions' contents (Tom)
+ </para>
+
+ <para>
+ This is very substantially more accurate than the regular <literal>GROUP
+ BY</literal> estimate for certain boolean tests like <replaceable>col</replaceable>
+ <literal>IS NULL</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix PL/PgSQL to not fail when a <literal>FOR</literal> loop's target variable
+ is a record containing composite-type fields (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix PL/Tcl to behave correctly with Tcl 8.5, and to be more careful
+ about the encoding of data sent to or from Tcl (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, work around a Microsoft bug by preventing
+ <application>libpq</application> from trying to send more than 64kB per system call
+ (Magnus)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve <application>pg_dump</application> and <application>pg_restore</application>'s
+ error reporting after failure to send a SQL command (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>pg_ctl</application> to properly preserve postmaster
+ command-line arguments across a <literal>restart</literal> (Bruce)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2008f (for
+ DST law changes in Argentina, Bahamas, Brazil, Mauritius, Morocco,
+ Pakistan, Palestine, and Paraguay)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-2-9">
<title>Release 8.2.9</title>
@@ -7544,6 +8130,182 @@
</sect2>
</sect1>
+ <sect1 id="release-8-1-14">
+ <title>Release 8.1.14</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2008-09-22</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.1.13.
+ 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.14</title>
+
+ <para>
+ A dump/restore is not required for those running 8.1.X.
+ However, if you are upgrading from a version earlier than 8.1.2,
+ see the release notes for 8.1.2.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Widen local lock counters from 32 to 64 bits (Tom)
+ </para>
+
+ <para>
+ This responds to reports that the counters could overflow in
+ sufficiently long transactions, leading to unexpected <quote>lock is
+ already held</quote> errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible duplicate output of tuples during a GiST index scan (Teodor)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add checks in executor startup to ensure that the tuples produced by an
+ <command>INSERT</command> or <command>UPDATE</command> will match the target table's
+ current rowtype (Tom)
+ </para>
+
+ <para>
+ <command>ALTER COLUMN TYPE</command>, followed by re-use of a previously
+ cached plan, could produce this type of situation. The check protects
+ against data corruption and/or crashes that could ensue.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <literal>AT TIME ZONE</literal> to first try to interpret its timezone
+ argument as a timezone abbreviation, and only try it as a full timezone
+ name if that fails, rather than the other way around as formerly (Tom)
+ </para>
+
+ <para>
+ The timestamp input functions have always resolved ambiguous zone names
+ in this order. Making <literal>AT TIME ZONE</literal> do so as well improves
+ consistency, and fixes a compatibility bug introduced in 8.1:
+ in ambiguous cases we now behave the same as 8.0 and before did,
+ since in the older versions <literal>AT TIME ZONE</literal> accepted
+ <emphasis>only</emphasis> abbreviations.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix datetime input functions to correctly detect integer overflow when
+ running on a 64-bit platform (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve performance of writing very long log messages to syslog (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix bug in backwards scanning of a cursor on a <literal>SELECT DISTINCT
+ ON</literal> query (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner bug with nested sub-select expressions (Tom)
+ </para>
+
+ <para>
+ If the outer sub-select has no direct dependency on the parent query,
+ but the inner one does, the outer value might not get recalculated
+ for new parent query rows.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner to estimate that <literal>GROUP BY</literal> expressions yielding
+ boolean results always result in two groups, regardless of the
+ expressions' contents (Tom)
+ </para>
+
+ <para>
+ This is very substantially more accurate than the regular <literal>GROUP
+ BY</literal> estimate for certain boolean tests like <replaceable>col</replaceable>
+ <literal>IS NULL</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix PL/PgSQL to not fail when a <literal>FOR</literal> loop's target variable
+ is a record containing composite-type fields (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix PL/Tcl to behave correctly with Tcl 8.5, and to be more careful
+ about the encoding of data sent to or from Tcl (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix PL/Python to work with Python 2.5
+ </para>
+
+ <para>
+ This is a back-port of fixes made during the 8.2 development cycle.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve <application>pg_dump</application> and <application>pg_restore</application>'s
+ error reporting after failure to send a SQL command (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>pg_ctl</application> to properly preserve postmaster
+ command-line arguments across a <literal>restart</literal> (Bruce)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2008f (for
+ DST law changes in Argentina, Bahamas, Brazil, Mauritius, Morocco,
+ Pakistan, Palestine, and Paraguay)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-1-13">
<title>Release 8.1.13</title>
@@ -11405,6 +12167,140 @@
</sect2>
</sect1>
+ <sect1 id="release-8-0-18">
+ <title>Release 8.0.18</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2008-09-22</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 8.0.17.
+ For information about new features in the 8.0 major release, see
+ <xref linkend="release-8-0"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 8.0.18</title>
+
+ <para>
+ A dump/restore is not required for those running 8.0.X.
+ However, if you are upgrading from a version earlier than 8.0.6,
+ see the release notes for 8.0.6.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Widen local lock counters from 32 to 64 bits (Tom)
+ </para>
+
+ <para>
+ This responds to reports that the counters could overflow in
+ sufficiently long transactions, leading to unexpected <quote>lock is
+ already held</quote> errors.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add checks in executor startup to ensure that the tuples produced by an
+ <command>INSERT</command> or <command>UPDATE</command> will match the target table's
+ current rowtype (Tom)
+ </para>
+
+ <para>
+ <command>ALTER COLUMN TYPE</command>, followed by re-use of a previously
+ cached plan, could produce this type of situation. The check protects
+ against data corruption and/or crashes that could ensue.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix datetime input functions to correctly detect integer overflow when
+ running on a 64-bit platform (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve performance of writing very long log messages to syslog (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix bug in backwards scanning of a cursor on a <literal>SELECT DISTINCT
+ ON</literal> query (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner to estimate that <literal>GROUP BY</literal> expressions yielding
+ boolean results always result in two groups, regardless of the
+ expressions' contents (Tom)
+ </para>
+
+ <para>
+ This is very substantially more accurate than the regular <literal>GROUP
+ BY</literal> estimate for certain boolean tests like <replaceable>col</replaceable>
+ <literal>IS NULL</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix PL/Tcl to behave correctly with Tcl 8.5, and to be more careful
+ about the encoding of data sent to or from Tcl (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix PL/Python to work with Python 2.5
+ </para>
+
+ <para>
+ This is a back-port of fixes made during the 8.2 development cycle.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve <application>pg_dump</application> and <application>pg_restore</application>'s
+ error reporting after failure to send a SQL command (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>pg_ctl</application> to properly preserve postmaster
+ command-line arguments across a <literal>restart</literal> (Bruce)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</application> release 2008f (for
+ DST law changes in Argentina, Bahamas, Brazil, Mauritius, Morocco,
+ Pakistan, Palestine, and Paraguay)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-8-0-17">
<title>Release 8.0.17</title>
@@ -15643,6 +16539,82 @@
</sect2>
</sect1>
+ <sect1 id="release-7-4-22">
+ <title>Release 7.4.22</title>
+
+ <note>
+ <title>Release date</title>
+ <simpara>2008-09-22</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 7.4.21.
+ For information about new features in the 7.4 major release, see
+ <xref linkend="release-7-4"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 7.4.22</title>
+
+ <para>
+ A dump/restore is not required for those running 7.4.X.
+ However, if you are upgrading from a version earlier than 7.4.11,
+ see the release notes for 7.4.11.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix datetime input functions to correctly detect integer overflow when
+ running on a 64-bit platform (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve performance of writing very long log messages to syslog (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix bug in backwards scanning of a cursor on a <literal>SELECT DISTINCT
+ ON</> query (Tom)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner to estimate that <literal>GROUP BY</> expressions yielding
+ boolean results always result in two groups, regardless of the
+ expressions' contents (Tom)
+ </para>
+
+ <para>
+ This is very substantially more accurate than the regular <literal>GROUP
+ BY</literal> estimate for certain boolean tests like <replaceable>col</replaceable>
+ <literal>IS NULL</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve <application>pg_dump</application> and <application>pg_restore</application>'s
+ error reporting after failure to send a SQL command (Tom)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-7-4-21">
<title>Release 7.4.21</title>
More information about the Trad
mailing list