Preliminary release notes for releases 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25,
7.4.29.
This commit is contained in:
parent
0c6b9308de
commit
8aad797362
@ -1,6 +1,110 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-7.4.sgml,v 1.5 2010/03/10 01:58:11 tgl Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-7.4.sgml,v 1.6 2010/05/12 23:20:49 tgl Exp $ -->
|
||||
<!-- See header comment in release.sgml about typical markup -->
|
||||
|
||||
<sect1 id="release-7-4-29">
|
||||
<title>Release 7.4.29</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2010-05-17</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 7.4.28.
|
||||
For information about new features in the 7.4 major release, see
|
||||
<xref linkend="release-7-4">.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <productname>PostgreSQL</> community will stop releasing updates
|
||||
for the 7.4.X release series in July 2010.
|
||||
Users are encouraged to update to a newer release branch soon.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to Version 7.4.29</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.26,
|
||||
see the release notes for 7.4.26.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes</title>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Do not allow an unprivileged user to reset superuser-only parameter
|
||||
settings (Alvaro)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
|
||||
ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
|
||||
a database he owns, this would remove all special parameter settings
|
||||
for the user or database, even ones that are only supposed to be
|
||||
changeable by a superuser. Now, the <command>ALTER</> will only
|
||||
remove the parameters that the user has permission to change.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Avoid possible crash during backend shutdown if shutdown occurs
|
||||
when a <literal>CONTEXT</> addition would be made to log entries (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In some cases the context-printing function would fail because the
|
||||
current transaction had already been rolled back when it came time
|
||||
to print a log message.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update pl/perl's <filename>ppport.h</> for modern Perl versions
|
||||
(Andrew)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
|
||||
interrupts promptly (Tatsuhito Kasahara)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Make server startup deal properly with the case that
|
||||
<function>shmget()</> returns <literal>EINVAL</> for an existing
|
||||
shared memory segment (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This behavior has been observed on BSD-derived kernels including OS X.
|
||||
It resulted in an entirely-misleading startup failure complaining that
|
||||
the shared memory request size was too large.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-7-4-28">
|
||||
<title>Release 7.4.28</title>
|
||||
|
||||
|
@ -1,6 +1,126 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.0.sgml,v 1.5 2010/03/10 01:58:11 tgl Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.0.sgml,v 1.6 2010/05/12 23:20:49 tgl Exp $ -->
|
||||
<!-- See header comment in release.sgml about typical markup -->
|
||||
|
||||
<sect1 id="release-8-0-25">
|
||||
<title>Release 8.0.25</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2010-05-17</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 8.0.24.
|
||||
For information about new features in the 8.0 major release, see
|
||||
<xref linkend="release-8-0">.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <productname>PostgreSQL</> community will stop releasing updates
|
||||
for the 8.0.X release series in July 2010.
|
||||
Users are encouraged to update to a newer release branch soon.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to Version 8.0.25</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.22,
|
||||
see the release notes for 8.0.22.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes</title>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Do not allow an unprivileged user to reset superuser-only parameter
|
||||
settings (Alvaro)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
|
||||
ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
|
||||
a database he owns, this would remove all special parameter settings
|
||||
for the user or database, even ones that are only supposed to be
|
||||
changeable by a superuser. Now, the <command>ALTER</> will only
|
||||
remove the parameters that the user has permission to change.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Avoid possible crash during backend shutdown if shutdown occurs
|
||||
when a <literal>CONTEXT</> addition would be made to log entries (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In some cases the context-printing function would fail because the
|
||||
current transaction had already been rolled back when it came time
|
||||
to print a log message.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update pl/perl's <filename>ppport.h</> for modern Perl versions
|
||||
(Andrew)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Prevent infinite recursion in <application>psql</> when expanding
|
||||
a variable that refers to itself (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
|
||||
interrupts promptly (Tatsuhito Kasahara)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Make server startup deal properly with the case that
|
||||
<function>shmget()</> returns <literal>EINVAL</> for an existing
|
||||
shared memory segment (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This behavior has been observed on BSD-derived kernels including OS X.
|
||||
It resulted in an entirely-misleading startup failure complaining that
|
||||
the shared memory request size was too large.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update time zone data files to <application>tzdata</> release 2010j
|
||||
for DST law changes in Argentina, Australian Antarctic, Bangladesh,
|
||||
Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia;
|
||||
also historical corrections for Taiwan.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-8-0-24">
|
||||
<title>Release 8.0.24</title>
|
||||
|
||||
|
@ -1,6 +1,120 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.1.sgml,v 1.5 2010/03/10 01:58:11 tgl Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.1.sgml,v 1.6 2010/05/12 23:20:49 tgl Exp $ -->
|
||||
<!-- See header comment in release.sgml about typical markup -->
|
||||
|
||||
<sect1 id="release-8-1-21">
|
||||
<title>Release 8.1.21</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2010-05-17</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 8.1.20.
|
||||
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.21</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.18,
|
||||
see the release notes for 8.1.18.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes</title>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Do not allow an unprivileged user to reset superuser-only parameter
|
||||
settings (Alvaro)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
|
||||
ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
|
||||
a database he owns, this would remove all special parameter settings
|
||||
for the user or database, even ones that are only supposed to be
|
||||
changeable by a superuser. Now, the <command>ALTER</> will only
|
||||
remove the parameters that the user has permission to change.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Avoid possible crash during backend shutdown if shutdown occurs
|
||||
when a <literal>CONTEXT</> addition would be made to log entries (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In some cases the context-printing function would fail because the
|
||||
current transaction had already been rolled back when it came time
|
||||
to print a log message.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update pl/perl's <filename>ppport.h</> for modern Perl versions
|
||||
(Andrew)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Prevent infinite recursion in <application>psql</> when expanding
|
||||
a variable that refers to itself (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
|
||||
interrupts promptly (Tatsuhito Kasahara)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Make server startup deal properly with the case that
|
||||
<function>shmget()</> returns <literal>EINVAL</> for an existing
|
||||
shared memory segment (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This behavior has been observed on BSD-derived kernels including OS X.
|
||||
It resulted in an entirely-misleading startup failure complaining that
|
||||
the shared memory request size was too large.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update time zone data files to <application>tzdata</> release 2010j
|
||||
for DST law changes in Argentina, Australian Antarctic, Bangladesh,
|
||||
Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia;
|
||||
also historical corrections for Taiwan.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-8-1-20">
|
||||
<title>Release 8.1.20</title>
|
||||
|
||||
|
@ -1,6 +1,167 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.2.sgml,v 1.5 2010/03/10 01:58:11 tgl Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.2.sgml,v 1.6 2010/05/12 23:20:49 tgl Exp $ -->
|
||||
<!-- See header comment in release.sgml about typical markup -->
|
||||
|
||||
<sect1 id="release-8-2-17">
|
||||
<title>Release 8.2.17</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2010-05-17</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 8.2.16.
|
||||
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.17</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.14,
|
||||
see the release notes for 8.2.14.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes</title>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix possible crash if a cache reset message is received during
|
||||
rebuild of a relcache entry (Heikki)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This error was introduced in 8.2.16 while fixing a related failure.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Do not allow an unprivileged user to reset superuser-only parameter
|
||||
settings (Alvaro)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
|
||||
ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
|
||||
a database he owns, this would remove all special parameter settings
|
||||
for the user or database, even ones that are only supposed to be
|
||||
changeable by a superuser. Now, the <command>ALTER</> will only
|
||||
remove the parameters that the user has permission to change.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Avoid possible crash during backend shutdown if shutdown occurs
|
||||
when a <literal>CONTEXT</> addition would be made to log entries (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In some cases the context-printing function would fail because the
|
||||
current transaction had already been rolled back when it came time
|
||||
to print a log message.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update pl/perl's <filename>ppport.h</> for modern Perl versions
|
||||
(Andrew)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Prevent infinite recursion in <application>psql</> when expanding
|
||||
a variable that refers to itself (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix <application>psql</>'s <literal>\copy</> to not add spaces around
|
||||
a dot within <literal>\copy (select ...)</> (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Addition of spaces around the decimal point in a numeric literal would
|
||||
result in a syntax error.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
|
||||
interrupts promptly (Tatsuhito Kasahara)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Make server startup deal properly with the case that
|
||||
<function>shmget()</> returns <literal>EINVAL</> for an existing
|
||||
shared memory segment (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This behavior has been observed on BSD-derived kernels including OS X.
|
||||
It resulted in an entirely-misleading startup failure complaining that
|
||||
the shared memory request size was too large.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Avoid possible crashes in syslogger process on Windows (Heikki)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Deal more robustly with incomplete time zone information in the
|
||||
Windows registry (Magnus)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update the set of known Windows time zone names (Magnus)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update time zone data files to <application>tzdata</> release 2010j
|
||||
for DST law changes in Argentina, Australian Antarctic, Bangladesh,
|
||||
Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia;
|
||||
also historical corrections for Taiwan.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Also, add <literal>PKST</> (Pakistan Summer Time) to the default set of
|
||||
timezone abbreviations.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-8-2-16">
|
||||
<title>Release 8.2.16</title>
|
||||
|
||||
|
@ -1,6 +1,195 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.3.sgml,v 1.5 2010/03/10 01:58:11 tgl Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.3.sgml,v 1.6 2010/05/12 23:20:49 tgl Exp $ -->
|
||||
<!-- See header comment in release.sgml about typical markup -->
|
||||
|
||||
<sect1 id="release-8-3-11">
|
||||
<title>Release 8.3.11</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2010-05-17</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 8.3.10.
|
||||
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.11</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.8,
|
||||
see the release notes for 8.3.8.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes</title>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix possible crash if a cache reset message is received during
|
||||
rebuild of a relcache entry (Heikki)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This error was introduced in 8.3.10 while fixing a related failure.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Apply per-function GUC settings while running the language validator
|
||||
for the function (Itagaki Takahiro)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This avoids failures if the function's code is invalid without the
|
||||
setting; an example is that SQL functions may not parse if the
|
||||
<varname>search_path</> is not correct.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Do not allow an unprivileged user to reset superuser-only parameter
|
||||
settings (Alvaro)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
|
||||
ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
|
||||
a database he owns, this would remove all special parameter settings
|
||||
for the user or database, even ones that are only supposed to be
|
||||
changeable by a superuser. Now, the <command>ALTER</> will only
|
||||
remove the parameters that the user has permission to change.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Avoid possible crash during backend shutdown if shutdown occurs
|
||||
when a <literal>CONTEXT</> addition would be made to log entries (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In some cases the context-printing function would fail because the
|
||||
current transaction had already been rolled back when it came time
|
||||
to print a log message.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure the archiver process responds to changes in
|
||||
<varname>archive_command</> as soon as possible (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update pl/perl's <filename>ppport.h</> for modern Perl versions
|
||||
(Andrew)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Prevent infinite recursion in <application>psql</> when expanding
|
||||
a variable that refers to itself (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix <application>psql</>'s <literal>\copy</> to not add spaces around
|
||||
a dot within <literal>\copy (select ...)</> (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Addition of spaces around the decimal point in a numeric literal would
|
||||
result in a syntax error.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix unnecessary <quote>GIN indexes do not support whole-index scans</>
|
||||
errors for unsatisfiable queries using <filename>contrib/intarray</>
|
||||
operators (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
|
||||
interrupts promptly (Tatsuhito Kasahara)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Make server startup deal properly with the case that
|
||||
<function>shmget()</> returns <literal>EINVAL</> for an existing
|
||||
shared memory segment (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This behavior has been observed on BSD-derived kernels including OS X.
|
||||
It resulted in an entirely-misleading startup failure complaining that
|
||||
the shared memory request size was too large.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Avoid possible crashes in syslogger process on Windows (Heikki)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Deal more robustly with incomplete time zone information in the
|
||||
Windows registry (Magnus)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update the set of known Windows time zone names (Magnus)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update time zone data files to <application>tzdata</> release 2010j
|
||||
for DST law changes in Argentina, Australian Antarctic, Bangladesh,
|
||||
Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia;
|
||||
also historical corrections for Taiwan.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Also, add <literal>PKST</> (Pakistan Summer Time) to the default set of
|
||||
timezone abbreviations.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-8-3-10">
|
||||
<title>Release 8.3.10</title>
|
||||
|
||||
|
@ -1,6 +1,257 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.4.sgml,v 1.17 2010/03/10 01:58:11 tgl Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-8.4.sgml,v 1.18 2010/05/12 23:20:49 tgl Exp $ -->
|
||||
<!-- See header comment in release.sgml about typical markup -->
|
||||
|
||||
<sect1 id="release-8-4-4">
|
||||
<title>Release 8.4.4</title>
|
||||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2010-05-17</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
This release contains a variety of fixes from 8.4.3.
|
||||
For information about new features in the 8.4 major release, see
|
||||
<xref linkend="release-8-4">.
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to Version 8.4.4</title>
|
||||
|
||||
<para>
|
||||
A dump/restore is not required for those running 8.4.X.
|
||||
However, if you are upgrading from a version earlier than 8.4.2,
|
||||
see the release notes for 8.4.2.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes</title>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix error during WAL replay of <literal>ALTER ... SET TABLESPACE</>
|
||||
(Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
When <varname>archive_mode</> is on, <literal>ALTER ... SET TABLESPACE</>
|
||||
generates a WAL record whose replay logic was incorrect. It could write
|
||||
the data to the wrong place, leading to possibly-unrecoverable data
|
||||
corruption. Data corruption would be observed on standby slaves, and
|
||||
could occur on the master as well if a database crash and recovery
|
||||
occurred after committing the <literal>ALTER</> and before the next
|
||||
checkpoint.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix possible crash if a cache reset message is received during
|
||||
rebuild of a relcache entry (Heikki)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This error was introduced in 8.4.3 while fixing a related failure.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Apply per-function GUC settings while running the language validator
|
||||
for the function (Itagaki Takahiro)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This avoids failures if the function's code is invalid without the
|
||||
setting; an example is that SQL functions may not parse if the
|
||||
<varname>search_path</> is not correct.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Do constraint exclusion for inherited <command>UPDATE</> and
|
||||
<command>DELETE</> target tables when
|
||||
<varname>constraint_exclusion</> = <literal>partition</> (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Due to an oversight, this setting previously only caused constraint
|
||||
exclusion to be checked in <command>SELECT</> commands.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Do not allow an unprivileged user to reset superuser-only parameter
|
||||
settings (Alvaro)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Previously, if an unprivileged user ran <literal>ALTER USER ... RESET
|
||||
ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for
|
||||
a database he owns, this would remove all special parameter settings
|
||||
for the user or database, even ones that are only supposed to be
|
||||
changeable by a superuser. Now, the <command>ALTER</> will only
|
||||
remove the parameters that the user has permission to change.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Avoid possible crash during backend shutdown if shutdown occurs
|
||||
when a <literal>CONTEXT</> addition would be made to log entries (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In some cases the context-printing function would fail because the
|
||||
current transaction had already been rolled back when it came time
|
||||
to print a log message.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix erroneous handling of <literal>%r</> parameter in
|
||||
<varname>recovery_end_command</> (Heikki)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The value always came out zero.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure the archiver process responds to changes in
|
||||
<varname>archive_command</> as soon as possible (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix pl/pgsql's <literal>CASE</> statement to not fail when the
|
||||
case expression is a query that returns no rows (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update pl/perl's <filename>ppport.h</> for modern Perl versions
|
||||
(Andrew)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix assorted memory leaks in pl/python (Andreas Freund, Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Handle empty-string connect parameters properly in ecpg (Michael)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Prevent infinite recursion in <application>psql</> when expanding
|
||||
a variable that refers to itself (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix <application>psql</>'s <literal>\copy</> to not add spaces around
|
||||
a dot within <literal>\copy (select ...)</> (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Addition of spaces around the decimal point in a numeric literal would
|
||||
result in a syntax error.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Avoid formatting failure in <application>psql</> when running in a
|
||||
locale context that doesn't match the <varname>client_encoding</>
|
||||
(Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Fix unnecessary <quote>GIN indexes do not support whole-index scans</>
|
||||
errors for unsatisfiable queries using <filename>contrib/intarray</>
|
||||
operators (Tom)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Ensure that <filename>contrib/pgstattuple</> functions respond to cancel
|
||||
interrupts promptly (Tatsuhito Kasahara)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Make server startup deal properly with the case that
|
||||
<function>shmget()</> returns <literal>EINVAL</> for an existing
|
||||
shared memory segment (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This behavior has been observed on BSD-derived kernels including OS X.
|
||||
It resulted in an entirely-misleading startup failure complaining that
|
||||
the shared memory request size was too large.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Avoid possible crashes in syslogger process on Windows (Heikki)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Deal more robustly with incomplete time zone information in the
|
||||
Windows registry (Magnus)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update the set of known Windows time zone names (Magnus)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Update time zone data files to <application>tzdata</> release 2010j
|
||||
for DST law changes in Argentina, Australian Antarctic, Bangladesh,
|
||||
Mexico, Morocco, Pakistan, Palestine, Russia, Syria, Tunisia;
|
||||
also historical corrections for Taiwan.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Also, add <literal>PKST</> (Pakistan Summer Time) to the default set of
|
||||
timezone abbreviations.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-8-4-3">
|
||||
<title>Release 8.4.3</title>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user