|
|
|
|
@ -1,4 +1,4 @@ |
|
|
|
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.582 2008/06/04 03:16:02 tgl Exp $ --> |
|
|
|
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.583 2008/06/07 22:10:38 tgl Exp $ --> |
|
|
|
|
<!-- |
|
|
|
|
|
|
|
|
|
Typical markup: |
|
|
|
|
@ -63,12 +63,66 @@ do it for earlier branch release files. |
|
|
|
|
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 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()</> 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</>, which is subtly incorrect: it should |
|
|
|
|
be <literal>(-42)::integer</> due to operator precedence rules. |
|
|
|
|
Usually this would make little difference, but it could interact with |
|
|
|
|
another recent patch to cause |
|
|
|
|
<productname>PostgreSQL</> to reject what had been a valid |
|
|
|
|
<command>SELECT DISTINCT</> view query. Since this could result in |
|
|
|
|
<application>pg_dump</> 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-3-2"> |
|
|
|
|
<title>Release 8.3.2</title> |
|
|
|
|
|
|
|
|
|
<note> |
|
|
|
|
<title>Release date</title> |
|
|
|
|
<simpara>2008-06-09</simpara> |
|
|
|
|
<simpara>never released</simpara> |
|
|
|
|
</note> |
|
|
|
|
|
|
|
|
|
<para> |
|
|
|
|
@ -3349,12 +3403,66 @@ current_date < 2017-11-17 |
|
|
|
|
</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 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()</> 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</>, which is subtly incorrect: it should |
|
|
|
|
be <literal>(-42)::integer</> due to operator precedence rules. |
|
|
|
|
Usually this would make little difference, but it could interact with |
|
|
|
|
another recent patch to cause |
|
|
|
|
<productname>PostgreSQL</> to reject what had been a valid |
|
|
|
|
<command>SELECT DISTINCT</> view query. Since this could result in |
|
|
|
|
<application>pg_dump</> 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-2-8"> |
|
|
|
|
<title>Release 8.2.8</title> |
|
|
|
|
|
|
|
|
|
<note> |
|
|
|
|
<title>Release date</title> |
|
|
|
|
<simpara>2008-06-09</simpara> |
|
|
|
|
<simpara>never released</simpara> |
|
|
|
|
</note> |
|
|
|
|
|
|
|
|
|
<para> |
|
|
|
|
@ -7322,12 +7430,66 @@ current_date < 2017-11-17 |
|
|
|
|
</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 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()</> 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</>, which is subtly incorrect: it should |
|
|
|
|
be <literal>(-42)::integer</> due to operator precedence rules. |
|
|
|
|
Usually this would make little difference, but it could interact with |
|
|
|
|
another recent patch to cause |
|
|
|
|
<productname>PostgreSQL</> to reject what had been a valid |
|
|
|
|
<command>SELECT DISTINCT</> view query. Since this could result in |
|
|
|
|
<application>pg_dump</> 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-1-12"> |
|
|
|
|
<title>Release 8.1.12</title> |
|
|
|
|
|
|
|
|
|
<note> |
|
|
|
|
<title>Release date</title> |
|
|
|
|
<simpara>2008-06-09</simpara> |
|
|
|
|
<simpara>never released</simpara> |
|
|
|
|
</note> |
|
|
|
|
|
|
|
|
|
<para> |
|
|
|
|
@ -11000,12 +11162,66 @@ psql -t -f fixseq.sql db1 | psql -e db1 |
|
|
|
|
</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()</> 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</>, which is subtly incorrect: it should |
|
|
|
|
be <literal>(-42)::integer</> due to operator precedence rules. |
|
|
|
|
Usually this would make little difference, but it could interact with |
|
|
|
|
another recent patch to cause |
|
|
|
|
<productname>PostgreSQL</> to reject what had been a valid |
|
|
|
|
<command>SELECT DISTINCT</> view query. Since this could result in |
|
|
|
|
<application>pg_dump</> 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> |
|
|
|
|
@ -15094,12 +15310,66 @@ typedefs (Michael)</para></listitem> |
|
|
|
|
</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()</> 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</>, which is subtly incorrect: it should |
|
|
|
|
be <literal>(-42)::integer</> due to operator precedence rules. |
|
|
|
|
Usually this would make little difference, but it could interact with |
|
|
|
|
another recent patch to cause |
|
|
|
|
<productname>PostgreSQL</> to reject what had been a valid |
|
|
|
|
<command>SELECT DISTINCT</> view query. Since this could result in |
|
|
|
|
<application>pg_dump</> 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> |
|
|
|
|
|
Tom Lane
18 years ago