From 2d3f41a3707bf88092636c1017267bdec70e09aa Mon Sep 17 00:00:00 2001 From: Tom Lane <tgl@sss.pgh.pa.us> Date: Tue, 9 Jun 2015 14:33:43 -0400 Subject: [PATCH] Release notes for 9.4.4, 9.3.9, 9.2.13, 9.1.18, 9.0.22. --- doc/src/sgml/release-9.0.sgml | 74 +++++++++++++++++++++++++++++++++++ doc/src/sgml/release-9.1.sgml | 68 ++++++++++++++++++++++++++++++++ doc/src/sgml/release-9.2.sgml | 68 ++++++++++++++++++++++++++++++++ 3 files changed, 210 insertions(+) diff --git a/doc/src/sgml/release-9.0.sgml b/doc/src/sgml/release-9.0.sgml index 80cd1c43cdc..736b6dda637 100644 --- a/doc/src/sgml/release-9.0.sgml +++ b/doc/src/sgml/release-9.0.sgml @@ -1,6 +1,80 @@ <!-- doc/src/sgml/release-9.0.sgml --> <!-- See header comment in release.sgml about typical markup --> + <sect1 id="release-9-0-22"> + <title>Release 9.0.22</title> + + <note> + <title>Release Date</title> + <simpara>2015-06-12</simpara> + </note> + + <para> + This release contains a small number of fixes from 9.0.21. + For information about new features in the 9.0 major release, see + <xref linkend="release-9-0">. + </para> + + <para> + The <productname>PostgreSQL</> community will stop releasing updates + for the 9.0.X release series in September 2015. + Users are encouraged to update to a newer release branch soon. + </para> + + <sect2> + <title>Migration to Version 9.0.22</title> + + <para> + A dump/restore is not required for those running 9.0.X. + </para> + + <para> + However, if you are upgrading from a version earlier than 9.0.18, + see <xref linkend="release-9-0-18">. + </para> + + </sect2> + + <sect2> + <title>Changes</title> + + <itemizedlist> + + <listitem> + <para> + Fix rare failure to invalidate relation cache init file (Tom Lane) + </para> + + <para> + With just the wrong timing of concurrent activity, a <command>VACUUM + FULL</> on a system catalog might fail to update the <quote>init file</> + that's used to avoid cache-loading work for new sessions. This would + result in later sessions being unable to access that catalog at all. + This is a very ancient bug, but it's so hard to trigger that no + reproducible case had been seen until recently. + </para> + </listitem> + + <listitem> + <para> + Avoid deadlock between incoming sessions and <literal>CREATE/DROP + DATABASE</> (Tom Lane) + </para> + + <para> + A new session starting in a database that is the target of + a <command>DROP DATABASE</> command, or is the template for + a <command>CREATE DATABASE</> command, could cause the command to wait + for five seconds and then fail, even if the new session would have + exited before that. + </para> + </listitem> + + </itemizedlist> + + </sect2> + </sect1> + <sect1 id="release-9-0-21"> <title>Release 9.0.21</title> diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml index 8306cfab039..a97ec57276f 100644 --- a/doc/src/sgml/release-9.1.sgml +++ b/doc/src/sgml/release-9.1.sgml @@ -1,6 +1,74 @@ <!-- doc/src/sgml/release-9.1.sgml --> <!-- See header comment in release.sgml about typical markup --> + <sect1 id="release-9-1-18"> + <title>Release 9.1.18</title> + + <note> + <title>Release Date</title> + <simpara>2015-06-12</simpara> + </note> + + <para> + This release contains a small number of fixes from 9.1.17. + For information about new features in the 9.1 major release, see + <xref linkend="release-9-1">. + </para> + + <sect2> + <title>Migration to Version 9.1.18</title> + + <para> + A dump/restore is not required for those running 9.1.X. + </para> + + <para> + However, if you are upgrading from a version earlier than 9.1.16, + see <xref linkend="release-9-1-16">. + </para> + + </sect2> + + <sect2> + <title>Changes</title> + + <itemizedlist> + + <listitem> + <para> + Fix rare failure to invalidate relation cache init file (Tom Lane) + </para> + + <para> + With just the wrong timing of concurrent activity, a <command>VACUUM + FULL</> on a system catalog might fail to update the <quote>init file</> + that's used to avoid cache-loading work for new sessions. This would + result in later sessions being unable to access that catalog at all. + This is a very ancient bug, but it's so hard to trigger that no + reproducible case had been seen until recently. + </para> + </listitem> + + <listitem> + <para> + Avoid deadlock between incoming sessions and <literal>CREATE/DROP + DATABASE</> (Tom Lane) + </para> + + <para> + A new session starting in a database that is the target of + a <command>DROP DATABASE</> command, or is the template for + a <command>CREATE DATABASE</> command, could cause the command to wait + for five seconds and then fail, even if the new session would have + exited before that. + </para> + </listitem> + + </itemizedlist> + + </sect2> + </sect1> + <sect1 id="release-9-1-17"> <title>Release 9.1.17</title> diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml index ef4ce98e538..d91328e7c1e 100644 --- a/doc/src/sgml/release-9.2.sgml +++ b/doc/src/sgml/release-9.2.sgml @@ -1,6 +1,74 @@ <!-- doc/src/sgml/release-9.2.sgml --> <!-- See header comment in release.sgml about typical markup --> + <sect1 id="release-9-2-13"> + <title>Release 9.2.13</title> + + <note> + <title>Release Date</title> + <simpara>2015-06-12</simpara> + </note> + + <para> + This release contains a small number of fixes from 9.2.12. + For information about new features in the 9.2 major release, see + <xref linkend="release-9-2">. + </para> + + <sect2> + <title>Migration to Version 9.2.13</title> + + <para> + A dump/restore is not required for those running 9.2.X. + </para> + + <para> + However, if you are upgrading from a version earlier than 9.2.11, + see <xref linkend="release-9-2-11">. + </para> + + </sect2> + + <sect2> + <title>Changes</title> + + <itemizedlist> + + <listitem> + <para> + Fix rare failure to invalidate relation cache init file (Tom Lane) + </para> + + <para> + With just the wrong timing of concurrent activity, a <command>VACUUM + FULL</> on a system catalog might fail to update the <quote>init file</> + that's used to avoid cache-loading work for new sessions. This would + result in later sessions being unable to access that catalog at all. + This is a very ancient bug, but it's so hard to trigger that no + reproducible case had been seen until recently. + </para> + </listitem> + + <listitem> + <para> + Avoid deadlock between incoming sessions and <literal>CREATE/DROP + DATABASE</> (Tom Lane) + </para> + + <para> + A new session starting in a database that is the target of + a <command>DROP DATABASE</> command, or is the template for + a <command>CREATE DATABASE</> command, could cause the command to wait + for five seconds and then fail, even if the new session would have + exited before that. + </para> + </listitem> + + </itemizedlist> + + </sect2> + </sect1> + <sect1 id="release-9-2-12"> <title>Release 9.2.12</title> -- GitLab