|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/release-7.4.sgml,v 1.1.10.5 2010/03/10 01:59:30 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/release-7.4.sgml,v 1.1.10.6 2010/05/12 23:28:06 tgl Exp $ --> |
2 | 2 | <!-- See header comment in release.sgml about typical markup -->
|
3 | 3 |
|
| 4 | + <sect1 id="release-7-4-29"> |
| 5 | + <title>Release 7.4.29</title> |
| 6 | + |
| 7 | + <note> |
| 8 | + <title>Release date</title> |
| 9 | + <simpara>2010-05-17</simpara> |
| 10 | + </note> |
| 11 | + |
| 12 | + <para> |
| 13 | + This release contains a variety of fixes from 7.4.28. |
| 14 | + For information about new features in the 7.4 major release, see |
| 15 | + <xref linkend="release-7-4">. |
| 16 | + </para> |
| 17 | + |
| 18 | + <para> |
| 19 | + The <productname>PostgreSQL</> community will stop releasing updates |
| 20 | + for the 7.4.X release series in July 2010. |
| 21 | + Users are encouraged to update to a newer release branch soon. |
| 22 | + </para> |
| 23 | + |
| 24 | + <sect2> |
| 25 | + <title>Migration to Version 7.4.29</title> |
| 26 | + |
| 27 | + <para> |
| 28 | + A dump/restore is not required for those running 7.4.X. |
| 29 | + However, if you are upgrading from a version earlier than 7.4.26, |
| 30 | + see the release notes for 7.4.26. |
| 31 | + </para> |
| 32 | + |
| 33 | + </sect2> |
| 34 | + |
| 35 | + <sect2> |
| 36 | + <title>Changes</title> |
| 37 | + |
| 38 | + <itemizedlist> |
| 39 | + |
| 40 | + <listitem> |
| 41 | + <para> |
| 42 | + Do not allow an unprivileged user to reset superuser-only parameter |
| 43 | + settings (Alvaro) |
| 44 | + </para> |
| 45 | + |
| 46 | + <para> |
| 47 | + Previously, if an unprivileged user ran <literal>ALTER USER ... RESET |
| 48 | + ALL</> for himself, or <literal>ALTER DATABASE ... RESET ALL</> for |
| 49 | + a database he owns, this would remove all special parameter settings |
| 50 | + for the user or database, even ones that are only supposed to be |
| 51 | + changeable by a superuser. Now, the <command>ALTER</> will only |
| 52 | + remove the parameters that the user has permission to change. |
| 53 | + </para> |
| 54 | + </listitem> |
| 55 | + |
| 56 | + <listitem> |
| 57 | + <para> |
| 58 | + Avoid possible crash during backend shutdown if shutdown occurs |
| 59 | + when a <literal>CONTEXT</> addition would be made to log entries (Tom) |
| 60 | + </para> |
| 61 | + |
| 62 | + <para> |
| 63 | + In some cases the context-printing function would fail because the |
| 64 | + current transaction had already been rolled back when it came time |
| 65 | + to print a log message. |
| 66 | + </para> |
| 67 | + </listitem> |
| 68 | + |
| 69 | + <listitem> |
| 70 | + <para> |
| 71 | + Update pl/perl's <filename>ppport.h</> for modern Perl versions |
| 72 | + (Andrew) |
| 73 | + </para> |
| 74 | + </listitem> |
| 75 | + |
| 76 | + <listitem> |
| 77 | + <para> |
| 78 | + Fix assorted memory leaks in pl/python (Andreas Freund, Tom) |
| 79 | + </para> |
| 80 | + </listitem> |
| 81 | + |
| 82 | + <listitem> |
| 83 | + <para> |
| 84 | + Ensure that <filename>contrib/pgstattuple</> functions respond to cancel |
| 85 | + interrupts promptly (Tatsuhito Kasahara) |
| 86 | + </para> |
| 87 | + </listitem> |
| 88 | + |
| 89 | + <listitem> |
| 90 | + <para> |
| 91 | + Make server startup deal properly with the case that |
| 92 | + <function>shmget()</> returns <literal>EINVAL</> for an existing |
| 93 | + shared memory segment (Tom) |
| 94 | + </para> |
| 95 | + |
| 96 | + <para> |
| 97 | + This behavior has been observed on BSD-derived kernels including OS X. |
| 98 | + It resulted in an entirely-misleading startup failure complaining that |
| 99 | + the shared memory request size was too large. |
| 100 | + </para> |
| 101 | + </listitem> |
| 102 | + |
| 103 | + </itemizedlist> |
| 104 | + |
| 105 | + </sect2> |
| 106 | + </sect1> |
| 107 | + |
4 | 108 | <sect1 id="release-7-4-28">
|
5 | 109 | <title>Release 7.4.28</title>
|
6 | 110 |
|
|