Skip to content

Commit bd85f77

Browse files
tglsfdctglsfdc
committed
Release notes for 9.4.3, 9.3.8, 9.2.12, 9.1.17, 9.0.21.
Also sneak entries for commits 97ff2a5 et al into the sections for the previous releases in the relevant branches. Those fixes did go out in the previous releases, but missed getting documented.
1 parent 9e79ca3 commit bd85f77

File tree

2 files changed

+196
-0
lines changed

2 files changed

+196
-0
lines changed

‎doc/src/sgml/release-9.0.sgml

+101
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,100 @@
11
<!-- doc/src/sgml/release-9.0.sgml -->
22
<!-- See header comment in release.sgml about typical markup -->
33

4+
<sect1 id="release-9-0-21">
5+
<title>Release 9.0.21</title>
6+
7+
<note>
8+
<title>Release Date</title>
9+
<simpara>2015-06-04</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a small number of fixes from 9.0.20.
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.21</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+
Avoid failures while <function>fsync</>'ing data directory during
46+
crash restart (Abhijit Menon-Sen, Tom Lane)
47+
</para>
48+
49+
<para>
50+
In the previous minor releases we added a patch to <function>fsync</>
51+
everything in the data directory after a crash. Unfortunately its
52+
response to any error condition was to fail, thereby preventing the
53+
server from starting up, even when the problem was quite harmless.
54+
An example is that an unwritable file in the data directory would
55+
prevent restart on some platforms; but it is common to make SSL
56+
certificate files unwritable by the server. Revise this behavior so
57+
that permissions failures are ignored altogether, and other types of
58+
failures are logged but do not prevent continuing.
59+
</para>
60+
</listitem>
61+
62+
<listitem>
63+
<para>
64+
Remove <application>configure</>'s check prohibiting linking to a
65+
threaded <application>libpython</>
66+
on <systemitem class="osname">OpenBSD</> (Tom Lane)
67+
</para>
68+
69+
<para>
70+
The failure this restriction was meant to prevent seems to not be a
71+
problem anymore on current <systemitem class="osname">OpenBSD</>
72+
versions.
73+
</para>
74+
</listitem>
75+
76+
<listitem>
77+
<para>
78+
Allow <application>libpq</> to use TLS protocol versions beyond v1
79+
(Noah Misch)
80+
</para>
81+
82+
<para>
83+
For a long time, <application>libpq</> was coded so that the only SSL
84+
protocol it would allow was TLS v1. Now that newer TLS versions are
85+
becoming popular, allow it to negotiate the highest commonly-supported
86+
TLS version with the server. (<productname>PostgreSQL</> servers were
87+
already capable of such negotiation, so no change is needed on the
88+
server side.) This is a back-patch of a change already released in
89+
9.4.0.
90+
</para>
91+
</listitem>
92+
93+
</itemizedlist>
94+
95+
</sect2>
96+
</sect1>
97+
498
<sect1 id="release-9-0-20">
599
<title>Release 9.0.20</title>
6100

@@ -169,6 +263,13 @@
169263
</para>
170264
</listitem>
171265

266+
<listitem>
267+
<para>
268+
Avoid <quote>cannot GetMultiXactIdMembers() during recovery</> error
269+
(&Aacute;lvaro Herrera)
270+
</para>
271+
</listitem>
272+
172273
<listitem>
173274
<para>
174275
Recursively <function>fsync()</> the data directory after a crash

‎doc/src/sgml/release-9.1.sgml

+95
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,94 @@
11
<!-- doc/src/sgml/release-9.1.sgml -->
22
<!-- See header comment in release.sgml about typical markup -->
33

4+
<sect1 id="release-9-1-17">
5+
<title>Release 9.1.17</title>
6+
7+
<note>
8+
<title>Release Date</title>
9+
<simpara>2015-06-04</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a small number of fixes from 9.1.16.
14+
For information about new features in the 9.1 major release, see
15+
<xref linkend="release-9-1">.
16+
</para>
17+
18+
<sect2>
19+
<title>Migration to Version 9.1.17</title>
20+
21+
<para>
22+
A dump/restore is not required for those running 9.1.X.
23+
</para>
24+
25+
<para>
26+
However, if you are upgrading from a version earlier than 9.1.16,
27+
see <xref linkend="release-9-1-16">.
28+
</para>
29+
30+
</sect2>
31+
32+
<sect2>
33+
<title>Changes</title>
34+
35+
<itemizedlist>
36+
37+
<listitem>
38+
<para>
39+
Avoid failures while <function>fsync</>'ing data directory during
40+
crash restart (Abhijit Menon-Sen, Tom Lane)
41+
</para>
42+
43+
<para>
44+
In the previous minor releases we added a patch to <function>fsync</>
45+
everything in the data directory after a crash. Unfortunately its
46+
response to any error condition was to fail, thereby preventing the
47+
server from starting up, even when the problem was quite harmless.
48+
An example is that an unwritable file in the data directory would
49+
prevent restart on some platforms; but it is common to make SSL
50+
certificate files unwritable by the server. Revise this behavior so
51+
that permissions failures are ignored altogether, and other types of
52+
failures are logged but do not prevent continuing.
53+
</para>
54+
</listitem>
55+
56+
<listitem>
57+
<para>
58+
Remove <application>configure</>'s check prohibiting linking to a
59+
threaded <application>libpython</>
60+
on <systemitem class="osname">OpenBSD</> (Tom Lane)
61+
</para>
62+
63+
<para>
64+
The failure this restriction was meant to prevent seems to not be a
65+
problem anymore on current <systemitem class="osname">OpenBSD</>
66+
versions.
67+
</para>
68+
</listitem>
69+
70+
<listitem>
71+
<para>
72+
Allow <application>libpq</> to use TLS protocol versions beyond v1
73+
(Noah Misch)
74+
</para>
75+
76+
<para>
77+
For a long time, <application>libpq</> was coded so that the only SSL
78+
protocol it would allow was TLS v1. Now that newer TLS versions are
79+
becoming popular, allow it to negotiate the highest commonly-supported
80+
TLS version with the server. (<productname>PostgreSQL</> servers were
81+
already capable of such negotiation, so no change is needed on the
82+
server side.) This is a back-patch of a change already released in
83+
9.4.0.
84+
</para>
85+
</listitem>
86+
87+
</itemizedlist>
88+
89+
</sect2>
90+
</sect1>
91+
492
<sect1 id="release-9-1-16">
593
<title>Release 9.1.16</title>
694

@@ -201,6 +289,13 @@
201289
</para>
202290
</listitem>
203291

292+
<listitem>
293+
<para>
294+
Avoid <quote>cannot GetMultiXactIdMembers() during recovery</> error
295+
(&Aacute;lvaro Herrera)
296+
</para>
297+
</listitem>
298+
204299
<listitem>
205300
<para>
206301
Recursively <function>fsync()</> the data directory after a crash

0 commit comments

Comments
 (0)