mirror of
https://github.com/postgres/postgres.git
synced 2025-05-29 16:21:20 +03:00
Update back-branch release notes.
This commit is contained in:
Tom Lane
parent
7266a78f7b
commit
09df79e8d7
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.400.2.54 2008/09/19 02:45:44 tgl Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.400.2.55 2008/10/30 22:23:11 tgl Exp $ -->
|
||||
<!--
|
||||
|
||||
Typical markup:
|
||||
@ -63,6 +63,155 @@ do it for earlier branch release files.
|
||||
review, so each item is truly a community effort.
|
||||
</para>
|
||||
|
||||
<sect1 id="release-8-1-15">
|
||||
<title>Release 8.1.15</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2008-11-03</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 8.1.14.
|
||||
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.15</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>
|
||||
Fix GiST index corruption due to marking the wrong index entry
|
||||
<quote>dead</> after a deletion (Teodor)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This would result in index searches failing to find rows they
|
||||
should have found.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix backend crash when the client encoding cannot represent a localized
|
||||
error message (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
We have addressed similar issues before, but it would still fail if
|
||||
the <quote>character has no equivalent</> message itself couldn't
|
||||
be converted. The fix is to disable localization and send the plain
|
||||
ASCII error message when we detect such a situation.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix possible crash when deeply nested functions are invoked from
|
||||
a trigger (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix mis-expansion of rule queries when a sub-<literal>SELECT</> appears
|
||||
in a function call in <literal>FROM</>, a multi-row <literal>VALUES</>
|
||||
list, or a <literal>RETURNING</> list (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The usual symptom of this problem is an <quote>unrecognized node type</>
|
||||
error.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure an error is reported when a newly-defined PL/pgSQL trigger
|
||||
function is invoked as a normal function (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Prevent possible collision of <structfield>relfilenode</> numbers
|
||||
when moving a table to another tablespace with <command>ALTER SET
|
||||
TABLESPACE</> (Heikki)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The command tried to re-use the existing filename, instead of
|
||||
picking one that is known unused in the destination directory.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix incorrect tsearch2 headline generation when single query
|
||||
item matches first word of text (Sushant Sinha)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix improper display of fractional seconds in interval values when
|
||||
using a non-ISO datestyle in an <option>--enable-integer-datetimes</>
|
||||
build (Ron Mayer)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure <function>SPI_getvalue</> and <function>SPI_getbinval</>
|
||||
behave correctly when the passed tuple and tuple descriptor have
|
||||
different numbers of columns (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This situation is normal when a table has had columns added or removed,
|
||||
but these two functions didn't handle it properly.
|
||||
The only likely consequence is an incorrect error indication.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix <application>ecpg</>'s parsing of <command>CREATE ROLE</> (Michael)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix recent breakage of <literal>pg_ctl restart</> (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update time zone data files to <application>tzdata</> release 2008i (for
|
||||
DST law changes in Argentina, Brazil, Mauritius, Syria)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-8-1-14">
|
||||
<title>Release 8.1.14</title>
|
||||
|
||||
@ -3984,6 +4133,117 @@ psql -t -f fixseq.sql db1 | psql -e db1
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-8-0-19">
|
||||
<title>Release 8.0.19</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2008-11-03</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 8.0.18.
|
||||
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.19</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>
|
||||
Fix backend crash when the client encoding cannot represent a localized
|
||||
error message (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
We have addressed similar issues before, but it would still fail if
|
||||
the <quote>character has no equivalent</> message itself couldn't
|
||||
be converted. The fix is to disable localization and send the plain
|
||||
ASCII error message when we detect such a situation.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix possible crash when deeply nested functions are invoked from
|
||||
a trigger (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure an error is reported when a newly-defined PL/pgSQL trigger
|
||||
function is invoked as a normal function (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix incorrect tsearch2 headline generation when single query
|
||||
item matches first word of text (Sushant Sinha)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix improper display of fractional seconds in interval values when
|
||||
using a non-ISO datestyle in an <option>--enable-integer-datetimes</>
|
||||
build (Ron Mayer)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure <function>SPI_getvalue</> and <function>SPI_getbinval</>
|
||||
behave correctly when the passed tuple and tuple descriptor have
|
||||
different numbers of columns (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This situation is normal when a table has had columns added or removed,
|
||||
but these two functions didn't handle it properly.
|
||||
The only likely consequence is an incorrect error indication.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix <application>ecpg</>'s parsing of <command>CREATE USER</> (Michael)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix recent breakage of <literal>pg_ctl restart</> (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update time zone data files to <application>tzdata</> release 2008i (for
|
||||
DST law changes in Argentina, Brazil, Mauritius, Syria)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-8-0-18">
|
||||
<title>Release 8.0.18</title>
|
||||
|
||||
@ -8266,6 +8526,90 @@ typedefs (Michael)</para></listitem>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-4-23">
|
||||
<title>Release 7.4.23</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2008-11-03</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 7.4.22.
|
||||
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.23</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 backend crash when the client encoding cannot represent a localized
|
||||
error message (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
We have addressed similar issues before, but it would still fail if
|
||||
the <quote>character has no equivalent</> message itself couldn't
|
||||
be converted. The fix is to disable localization and send the plain
|
||||
ASCII error message when we detect such a situation.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix incorrect tsearch2 headline generation when single query
|
||||
item matches first word of text (Sushant Sinha)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix improper display of fractional seconds in interval values when
|
||||
using a non-ISO datestyle in an <option>--enable-integer-datetimes</>
|
||||
build (Ron Mayer)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure <function>SPI_getvalue</> and <function>SPI_getbinval</>
|
||||
behave correctly when the passed tuple and tuple descriptor have
|
||||
different numbers of columns (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This situation is normal when a table has had columns added or removed,
|
||||
but these two functions didn't handle it properly.
|
||||
The only likely consequence is an incorrect error indication.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix <application>ecpg</>'s parsing of <command>CREATE USER</> (Michael)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-4-22">
|
||||
<title>Release 7.4.22</title>
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user