|
1 | 1 | <!-- doc/src/sgml/release-9.0.sgml -->
|
2 | 2 | <!-- See header comment in release.sgml about typical markup -->
|
3 | 3 |
|
| 4 | + <sect1 id="release-9-0-22"> |
| 5 | + <title>Release 9.0.22</title> |
| 6 | + |
| 7 | + <note> |
| 8 | + <title>Release Date</title> |
| 9 | + <simpara>2015-06-12</simpara> |
| 10 | + </note> |
| 11 | + |
| 12 | + <para> |
| 13 | + This release contains a small number of fixes from 9.0.21. |
| 14 | + For information about new features in the 9.0 major release, see |
| 15 | + <xref linkend="release-9-0">. |
| 16 | + </para> |
| 17 | + |
| 18 | + <para> |
| 19 | + The <productname>PostgreSQL</> community will stop releasing updates |
| 20 | + for the 9.0.X release series in September 2015. |
| 21 | + Users are encouraged to update to a newer release branch soon. |
| 22 | + </para> |
| 23 | + |
| 24 | + <sect2> |
| 25 | + <title>Migration to Version 9.0.22</title> |
| 26 | + |
| 27 | + <para> |
| 28 | + A dump/restore is not required for those running 9.0.X. |
| 29 | + </para> |
| 30 | + |
| 31 | + <para> |
| 32 | + However, if you are upgrading from a version earlier than 9.0.18, |
| 33 | + see <xref linkend="release-9-0-18">. |
| 34 | + </para> |
| 35 | + |
| 36 | + </sect2> |
| 37 | + |
| 38 | + <sect2> |
| 39 | + <title>Changes</title> |
| 40 | + |
| 41 | + <itemizedlist> |
| 42 | + |
| 43 | + <listitem> |
| 44 | + <para> |
| 45 | + Fix rare failure to invalidate relation cache init file (Tom Lane) |
| 46 | + </para> |
| 47 | + |
| 48 | + <para> |
| 49 | + With just the wrong timing of concurrent activity, a <command>VACUUM |
| 50 | + FULL</> on a system catalog might fail to update the <quote>init file</> |
| 51 | + that's used to avoid cache-loading work for new sessions. This would |
| 52 | + result in later sessions being unable to access that catalog at all. |
| 53 | + This is a very ancient bug, but it's so hard to trigger that no |
| 54 | + reproducible case had been seen until recently. |
| 55 | + </para> |
| 56 | + </listitem> |
| 57 | + |
| 58 | + <listitem> |
| 59 | + <para> |
| 60 | + Avoid deadlock between incoming sessions and <literal>CREATE/DROP |
| 61 | + DATABASE</> (Tom Lane) |
| 62 | + </para> |
| 63 | + |
| 64 | + <para> |
| 65 | + A new session starting in a database that is the target of |
| 66 | + a <command>DROP DATABASE</> command, or is the template for |
| 67 | + a <command>CREATE DATABASE</> command, could cause the command to wait |
| 68 | + for five seconds and then fail, even if the new session would have |
| 69 | + exited before that. |
| 70 | + </para> |
| 71 | + </listitem> |
| 72 | + |
| 73 | + </itemizedlist> |
| 74 | + |
| 75 | + </sect2> |
| 76 | + </sect1> |
| 77 | + |
4 | 78 | <sect1 id="release-9-0-21">
|
5 | 79 | <title>Release 9.0.21</title>
|
6 | 80 |
|
|
0 commit comments