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:
Tom Lane 2010-05-12 23:28:06 +00:00
parent 47bdd80dc1
commit 03bbb02999
1 changed files with 105 additions and 1 deletions

View File

@ -1,6 +1,110 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-7.4.sgml,v 1.1.10.5 2010/03/10 01:59:30 tgl Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/release-7.4.sgml,v 1.1.10.6 2010/05/12 23:28:06 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>