[Trad] [svn:pgfr] r1070 - traduc/trunk/postgresql

svncommit at kryskool.org svncommit at kryskool.org
Lun 9 Juin 10:02:28 CEST 2008


Auteur: gleu
Date: 2008-06-09 10:02:23 +0200 (lun, 09 jun 2008)
Nouvelle Révision: 1070

Modification:
   traduc/trunk/postgresql/release.xml
   traduc/trunk/postgresql/version.xml
Log:
ise à jour version 8.3.3.


Modified: traduc/trunk/postgresql/release.xml
===================================================================
--- traduc/trunk/postgresql/release.xml	2008-06-09 07:58:19 UTC (rev 1069)
+++ traduc/trunk/postgresql/release.xml	2008-06-09 08:02:23 UTC (rev 1070)
@@ -67,12 +67,79 @@
    review, so each item is truly a community effort.
   </para>
 
+ <sect1 id="release-8-3-3">
+  <title>Release 8.3.3</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>2008-06-12</simpara>
+  </note>
+
+  <para>
+   This release contains one serious and one minor bug fix over 8.3.2.
+   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.3</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>
+      Make <function>pg_get_ruledef()</function> parenthesize negative constants (Tom)
+     </para>
+
+     <para>
+      Before this fix, a negative constant in a view or rule might be dumped
+      as, say, <literal>-42::integer</literal>, which is subtly incorrect: it should
+      be <literal>(-42)::integer</literal> due to operator precedence rules.
+      Usually this would make little difference, but it could interact with
+      another recent patch to cause
+      <productname>PostgreSQL</productname> to reject what had been a valid
+      <command>SELECT DISTINCT</command> view query.  Since this could result in
+      <application>pg_dump</application> output failing to reload, it is being treated
+      as a high-priority fix.  The only released versions in which dump
+      output is actually incorrect are 8.3.1 and 8.2.7.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Make <command>ALTER AGGREGATE ... OWNER TO</command> update
+      <structname>pg_shdepend</structname> (Tom)
+     </para>
+
+     <para>
+      This oversight could lead to problems if the aggregate was later
+      involved in a <command>DROP OWNED</command> or <command>REASSIGN OWNED</command>
+      operation.
+     </para>
+    </listitem>
+
+   </itemizedlist>
+
+  </sect2>
+ </sect1>
+
  <sect1 id="release-8-3-2">
   <title>Release 8.3.2</title>
 
   <note>
   <title>Release date</title>
-  <simpara>2008-06-09</simpara>
+  <simpara>never released</simpara>
   </note>
 
   <para>
@@ -3351,12 +3418,79 @@
   </sect2>
  </sect1>
 
+ <sect1 id="release-8-2-9">
+  <title>Release 8.2.9</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>2008-06-12</simpara>
+  </note>
+
+  <para>
+   This release contains one serious and one minor bug fix over 8.2.8.
+   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.9</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>
+      Make <function>pg_get_ruledef()</function> parenthesize negative constants (Tom)
+     </para>
+
+     <para>
+      Before this fix, a negative constant in a view or rule might be dumped
+      as, say, <literal>-42::integer</literal>, which is subtly incorrect: it should
+      be <literal>(-42)::integer</literal> due to operator precedence rules.
+      Usually this would make little difference, but it could interact with
+      another recent patch to cause
+      <productname>PostgreSQL</productname> to reject what had been a valid
+      <command>SELECT DISTINCT</command> view query.  Since this could result in
+      <application>pg_dump</application> output failing to reload, it is being treated
+      as a high-priority fix.  The only released versions in which dump
+      output is actually incorrect are 8.3.1 and 8.2.7.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Make <command>ALTER AGGREGATE ... OWNER TO</command> update
+      <structname>pg_shdepend</structname> (Tom)
+     </para>
+
+     <para>
+      This oversight could lead to problems if the aggregate was later
+      involved in a <command>DROP OWNED</command> or <command>REASSIGN OWNED</command>
+      operation.
+     </para>
+    </listitem>
+
+   </itemizedlist>
+
+  </sect2>
+ </sect1>
+
  <sect1 id="release-8-2-8">
   <title>Release 8.2.8</title>
 
   <note>
   <title>Release date</title>
-  <simpara>2008-06-09</simpara>
+  <simpara>never released</simpara>
   </note>
 
   <para>
@@ -7410,12 +7544,79 @@
    </sect2>
   </sect1>
 
+ <sect1 id="release-8-1-13">
+  <title>Release 8.1.13</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>2008-06-12</simpara>
+  </note>
+
+  <para>
+   This release contains one serious and one minor bug fix over 8.1.12.
+   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.13</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>
+      Make <function>pg_get_ruledef()</function> parenthesize negative constants (Tom)
+     </para>
+
+     <para>
+      Before this fix, a negative constant in a view or rule might be dumped
+      as, say, <literal>-42::integer</literal>, which is subtly incorrect: it should
+      be <literal>(-42)::integer</literal> due to operator precedence rules.
+      Usually this would make little difference, but it could interact with
+      another recent patch to cause
+      <productname>PostgreSQL</productname> to reject what had been a valid
+      <command>SELECT DISTINCT</command> view query.  Since this could result in
+      <application>pg_dump</application> output failing to reload, it is being treated
+      as a high-priority fix.  The only released versions in which dump
+      output is actually incorrect are 8.3.1 and 8.2.7.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Make <command>ALTER AGGREGATE ... OWNER TO</command> update
+      <structname>pg_shdepend</structname> (Tom)
+     </para>
+
+     <para>
+      This oversight could lead to problems if the aggregate was later
+      involved in a <command>DROP OWNED</command> or <command>REASSIGN OWNED</command>
+      operation.
+     </para>
+    </listitem>
+
+   </itemizedlist>
+
+  </sect2>
+ </sect1>
+
  <sect1 id="release-8-1-12">
   <title>Release 8.1.12</title>
 
   <note>
   <title>Release date</title>
-  <simpara>2008-06-09</simpara>
+  <simpara>never released</simpara>
   </note>
 
   <para>
@@ -11204,12 +11405,66 @@
    </sect2>
   </sect1>
 
+ <sect1 id="release-8-0-17">
+  <title>Release 8.0.17</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>2008-06-12</simpara>
+  </note>
+
+  <para>
+   This release contains one serious bug fix over 8.0.16.
+   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.17</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>
+      Make <function>pg_get_ruledef()</function> parenthesize negative constants (Tom)
+     </para>
+
+     <para>
+      Before this fix, a negative constant in a view or rule might be dumped
+      as, say, <literal>-42::integer</literal>, which is subtly incorrect: it should
+      be <literal>(-42)::integer</literal> due to operator precedence rules.
+      Usually this would make little difference, but it could interact with
+      another recent patch to cause
+      <productname>PostgreSQL</productname> to reject what had been a valid
+      <command>SELECT DISTINCT</command> view query.  Since this could result in
+      <application>pg_dump</application> output failing to reload, it is being treated
+      as a high-priority fix.  The only released versions in which dump
+      output is actually incorrect are 8.3.1 and 8.2.7.
+     </para>
+    </listitem>
+
+   </itemizedlist>
+
+  </sect2>
+ </sect1>
+
  <sect1 id="release-8-0-16">
   <title>Release 8.0.16</title>
 
   <note>
   <title>Release date</title>
-  <simpara>2008-06-09</simpara>
+  <simpara>never released</simpara>
   </note>
 
   <para>
@@ -15388,12 +15643,66 @@
   </sect2>
  </sect1>
 
+ <sect1 id="release-7-4-21">
+  <title>Release 7.4.21</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>2008-06-12</simpara>
+  </note>
+
+  <para>
+   This release contains one serious bug fix over 7.4.20.
+   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.21</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>
+      Make <function>pg_get_ruledef()</function> parenthesize negative constants (Tom)
+     </para>
+
+     <para>
+      Before this fix, a negative constant in a view or rule might be dumped
+      as, say, <literal>-42::integer</literal>, which is subtly incorrect: it should
+      be <literal>(-42)::integer</literal> due to operator precedence rules.
+      Usually this would make little difference, but it could interact with
+      another recent patch to cause
+      <productname>PostgreSQL</productname> to reject what had been a valid
+      <command>SELECT DISTINCT</command> view query.  Since this could result in
+      <application>pg_dump</application> output failing to reload, it is being treated
+      as a high-priority fix.  The only released versions in which dump
+      output is actually incorrect are 8.3.1 and 8.2.7.
+     </para>
+    </listitem>
+
+   </itemizedlist>
+
+  </sect2>
+ </sect1>
+
  <sect1 id="release-7-4-20">
   <title>Release 7.4.20</title>
 
   <note>
   <title>Release date</title>
-  <simpara>2008-06-09</simpara>
+  <simpara>never released</simpara>
   </note>
 
   <para>

Modified: traduc/trunk/postgresql/version.xml
===================================================================
--- traduc/trunk/postgresql/version.xml	2008-06-09 07:58:19 UTC (rev 1069)
+++ traduc/trunk/postgresql/version.xml	2008-06-09 08:02:23 UTC (rev 1070)
@@ -1,2 +1,2 @@
-<!ENTITY version "8.3.2">
+<!ENTITY version "8.3.3">
 <!ENTITY majorversion "8.3">



More information about the Trad mailing list