database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-17 06:41:09 +03:00
Code Activity

Update back-branch release notes.

Browse Source
This commit is contained in:
Tom Lane
2008-09-19 02:45:33 +00:00
parent 466c89e808
commit c82cf66508
1 changed files with 619 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

620
doc/src/sgml/release.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.488.2.21 2008/06/08 21:46:26 tgl Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.488.2.22 2008/09/19 02:45:33 tgl Exp $ -->
<!--
Typical markup:
@ -63,6 +63,238 @@ do it for earlier branch release files.
review, so each item is truly a community effort.
</para>
<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</> (Alvaro)
</para>
<para>
This error may explain some recent reports of failure to remove old
<structname>pg_clog</> 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</> 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</> 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</> or <command>UPDATE</> will match the target table's
current rowtype (Tom)
</para>
<para>
<command>ALTER COLUMN TYPE</>, 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</> (Tom)
</para>
<para>
This would typically result in strange errors such as <quote>cache
lookup failed for relation NNN</>.
</para>
</listitem>
<listitem>
<para>
Fix <literal>AT TIME ZONE</> 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</> 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</> accepted
<emphasis>only</> 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</> (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 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</> 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</> estimate for certain boolean tests like <replaceable>col</>
<literal>IS NULL</>.
</para>
</listitem>
<listitem>
<para>
Fix PL/PgSQL to not fail when a <literal>FOR</> 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</> from trying to send more than 64kB per system call
(Magnus)
</para>
</listitem>
<listitem>
<para>
Improve <application>pg_dump</> and <application>pg_restore</>'s
error reporting after failure to send a SQL command (Tom)
</para>
</listitem>
<listitem>
<para>
Fix <application>pg_ctl</> to properly preserve postmaster
command-line arguments across a <literal>restart</> (Bruce)
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> 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>
@ -4103,6 +4335,182 @@ do it for earlier branch release files.
</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</> 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</> or <command>UPDATE</> will match the target table's
current rowtype (Tom)
</para>
<para>
<command>ALTER COLUMN TYPE</>, 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</> 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</> 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</> accepted
<emphasis>only</> 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</> 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</> 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</> estimate for certain boolean tests like <replaceable>col</>
<literal>IS NULL</>.
</para>
</listitem>
<listitem>
<para>
Fix PL/PgSQL to not fail when a <literal>FOR</> 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</> and <application>pg_restore</>'s
error reporting after failure to send a SQL command (Tom)
</para>
</listitem>
<listitem>
<para>
Fix <application>pg_ctl</> to properly preserve postmaster
command-line arguments across a <literal>restart</> (Bruce)
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> 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>
@ -7848,6 +8256,140 @@ psql -t -f fixseq.sql db1 | psql -e db1
</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</> errors.
</para>
</listitem>
<listitem>
<para>
Add checks in executor startup to ensure that the tuples produced by an
<command>INSERT</> or <command>UPDATE</> will match the target table's
current rowtype (Tom)
</para>
<para>
<command>ALTER COLUMN TYPE</>, 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</> 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</> estimate for certain boolean tests like <replaceable>col</>
<literal>IS NULL</>.
</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</> and <application>pg_restore</>'s
error reporting after failure to send a SQL command (Tom)
</para>
</listitem>
<listitem>
<para>
Fix <application>pg_ctl</> to properly preserve postmaster
command-line arguments across a <literal>restart</> (Bruce)
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> 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>
@ -11996,6 +12538,82 @@ typedefs (Michael)</para></listitem>
</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</> estimate for certain boolean tests like <replaceable>col</>
<literal>IS NULL</>.
</para>
</listitem>
<listitem>
<para>
Improve <application>pg_dump</> and <application>pg_restore</>'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>