Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit828fe49

Browse files
committed
Release notes for 9.5.3, 9.4.8, 9.3.13, 9.2.17, 9.1.22.
1 parent673bcea commit828fe49

File tree

5 files changed

+1357
-2
lines changed

5 files changed

+1357
-2
lines changed

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

Lines changed: 165 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,171 @@
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-22">
5+
<title>Release 9.1.22</title>
6+
7+
<note>
8+
<title>Release Date</title>
9+
<simpara>2016-05-12</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a variety of fixes from 9.1.21.
14+
For information about new features in the 9.1 major release, see
15+
<xref linkend="release-9-1">.
16+
</para>
17+
18+
<para>
19+
The <productname>PostgreSQL</> community will stop releasing updates
20+
for the 9.1.X release series in September 2016.
21+
Users are encouraged to update to a newer release branch soon.
22+
</para>
23+
24+
<sect2>
25+
<title>Migration to Version 9.1.22</title>
26+
27+
<para>
28+
A dump/restore is not required for those running 9.1.X.
29+
</para>
30+
31+
<para>
32+
However, if you are upgrading from a version earlier than 9.1.16,
33+
see <xref linkend="release-9-1-16">.
34+
</para>
35+
36+
</sect2>
37+
38+
<sect2>
39+
<title>Changes</title>
40+
41+
<itemizedlist>
42+
43+
<listitem>
44+
<para>
45+
Clear the OpenSSL error queue before OpenSSL calls, rather than
46+
assuming it's clear already; and make sure we leave it clear
47+
afterwards (Peter Geoghegan, Dave Vitek, Peter Eisentraut)
48+
</para>
49+
50+
<para>
51+
This change prevents problems when there are multiple connections
52+
using OpenSSL within a single process and not all the code involved
53+
follows the same rules for when to clear the error queue.
54+
Failures have been reported specifically when a client application
55+
uses SSL connections in <application>libpq</> concurrently with
56+
SSL connections using the PHP, Python, or Ruby wrappers for OpenSSL.
57+
It's possible for similar problems to arise within the server as well,
58+
if an extension module establishes an outgoing SSL connection.
59+
</para>
60+
</listitem>
61+
62+
<listitem>
63+
<para>
64+
Fix <quote>failed to build any <replaceable>N</>-way joins</quote>
65+
planner error with a full join enclosed in the right-hand side of a
66+
left join (Tom Lane)
67+
</para>
68+
</listitem>
69+
70+
<listitem>
71+
<para>
72+
Fix possible misbehavior of <literal>TH</>, <literal>th</>,
73+
and <literal>Y,YYY</> format codes in <function>to_timestamp()</>
74+
(Tom Lane)
75+
</para>
76+
77+
<para>
78+
These could advance off the end of the input string, causing subsequent
79+
format codes to read garbage.
80+
</para>
81+
</listitem>
82+
83+
<listitem>
84+
<para>
85+
Fix dumping of rules and views in which the <replaceable>array</>
86+
argument of a <literal><replaceable>value</> <replaceable>operator</>
87+
ANY (<replaceable>array</>)</literal> construct is a sub-SELECT
88+
(Tom Lane)
89+
</para>
90+
</listitem>
91+
92+
<listitem>
93+
<para>
94+
Make <application>pg_regress</> use a startup timeout from the
95+
<envar>PGCTLTIMEOUT</> environment variable, if that's set (Tom Lane)
96+
</para>
97+
98+
<para>
99+
This is for consistency with a behavior recently added
100+
to <application>pg_ctl</>; it eases automated testing on slow machines.
101+
</para>
102+
</listitem>
103+
104+
<listitem>
105+
<para>
106+
Fix <application>pg_upgrade</> to correctly restore extension
107+
membership for operator families containing only one operator class
108+
(Tom Lane)
109+
</para>
110+
111+
<para>
112+
In such a case, the operator family was restored into the new database,
113+
but it was no longer marked as part of the extension. This had no
114+
immediate ill effects, but would cause later <application>pg_dump</>
115+
runs to emit output that would cause (harmless) errors on restore.
116+
</para>
117+
</listitem>
118+
119+
<listitem>
120+
<para>
121+
Rename internal function <function>strtoi()</>
122+
to <function>strtoint()</> to avoid conflict with a NetBSD library
123+
function (Thomas Munro)
124+
</para>
125+
</listitem>
126+
127+
<listitem>
128+
<para>
129+
Fix reporting of errors from <function>bind()</>
130+
and <function>listen()</> system calls on Windows (Tom Lane)
131+
</para>
132+
</listitem>
133+
134+
<listitem>
135+
<para>
136+
Reduce verbosity of compiler output when building with Microsoft Visual
137+
Studio (Christian Ullrich)
138+
</para>
139+
</listitem>
140+
141+
<listitem>
142+
<para>
143+
Avoid possibly-unsafe use of Windows' <function>FormatMessage()</>
144+
function (Christian Ullrich)
145+
</para>
146+
147+
<para>
148+
Use the <literal>FORMAT_MESSAGE_IGNORE_INSERTS</> flag where
149+
appropriate. No live bug is known to exist here, but it seems like a
150+
good idea to be careful.
151+
</para>
152+
</listitem>
153+
154+
<listitem>
155+
<para>
156+
Update time zone data files to <application>tzdata</> release 2016d
157+
for DST law changes in Russia and Venezuela. There are new zone
158+
names <literal>Europe/Kirov</> and <literal>Asia/Tomsk</> to reflect
159+
the fact that these regions now have different time zone histories from
160+
adjacent regions.
161+
</para>
162+
</listitem>
163+
164+
</itemizedlist>
165+
166+
</sect2>
167+
</sect1>
168+
4169
<sect1 id="release-9-1-21">
5170
<title>Release 9.1.21</title>
6171

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

Lines changed: 196 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,202 @@
11
<!-- doc/src/sgml/release-9.2.sgml -->
22
<!-- See header comment in release.sgml about typical markup -->
33

4+
<sect1 id="release-9-2-17">
5+
<title>Release 9.2.17</title>
6+
7+
<note>
8+
<title>Release Date</title>
9+
<simpara>2016-05-12</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a variety of fixes from 9.2.16.
14+
For information about new features in the 9.2 major release, see
15+
<xref linkend="release-9-2">.
16+
</para>
17+
18+
<sect2>
19+
<title>Migration to Version 9.2.17</title>
20+
21+
<para>
22+
A dump/restore is not required for those running 9.2.X.
23+
</para>
24+
25+
<para>
26+
However, if you are upgrading from a version earlier than 9.2.11,
27+
see <xref linkend="release-9-2-11">.
28+
</para>
29+
30+
</sect2>
31+
32+
<sect2>
33+
<title>Changes</title>
34+
35+
<itemizedlist>
36+
37+
<listitem>
38+
<para>
39+
Clear the OpenSSL error queue before OpenSSL calls, rather than
40+
assuming it's clear already; and make sure we leave it clear
41+
afterwards (Peter Geoghegan, Dave Vitek, Peter Eisentraut)
42+
</para>
43+
44+
<para>
45+
This change prevents problems when there are multiple connections
46+
using OpenSSL within a single process and not all the code involved
47+
follows the same rules for when to clear the error queue.
48+
Failures have been reported specifically when a client application
49+
uses SSL connections in <application>libpq</> concurrently with
50+
SSL connections using the PHP, Python, or Ruby wrappers for OpenSSL.
51+
It's possible for similar problems to arise within the server as well,
52+
if an extension module establishes an outgoing SSL connection.
53+
</para>
54+
</listitem>
55+
56+
<listitem>
57+
<para>
58+
Fix <quote>failed to build any <replaceable>N</>-way joins</quote>
59+
planner error with a full join enclosed in the right-hand side of a
60+
left join (Tom Lane)
61+
</para>
62+
</listitem>
63+
64+
<listitem>
65+
<para>
66+
Fix incorrect handling of equivalence-class tests in multilevel
67+
nestloop plans (Tom Lane)
68+
</para>
69+
70+
<para>
71+
Given a three-or-more-way equivalence class of variables, such
72+
as <literal>X.X = Y.Y = Z.Z</>, it was possible for the planner to omit
73+
some of the tests needed to enforce that all the variables are actually
74+
equal, leading to join rows being output that didn't satisfy
75+
the <literal>WHERE</> clauses. For various reasons, erroneous plans
76+
were seldom selected in practice, so that this bug has gone undetected
77+
for a long time.
78+
</para>
79+
</listitem>
80+
81+
<listitem>
82+
<para>
83+
Fix possible misbehavior of <literal>TH</>, <literal>th</>,
84+
and <literal>Y,YYY</> format codes in <function>to_timestamp()</>
85+
(Tom Lane)
86+
</para>
87+
88+
<para>
89+
These could advance off the end of the input string, causing subsequent
90+
format codes to read garbage.
91+
</para>
92+
</listitem>
93+
94+
<listitem>
95+
<para>
96+
Fix dumping of rules and views in which the <replaceable>array</>
97+
argument of a <literal><replaceable>value</> <replaceable>operator</>
98+
ANY (<replaceable>array</>)</literal> construct is a sub-SELECT
99+
(Tom Lane)
100+
</para>
101+
</listitem>
102+
103+
<listitem>
104+
<para>
105+
Make <application>pg_regress</> use a startup timeout from the
106+
<envar>PGCTLTIMEOUT</> environment variable, if that's set (Tom Lane)
107+
</para>
108+
109+
<para>
110+
This is for consistency with a behavior recently added
111+
to <application>pg_ctl</>; it eases automated testing on slow machines.
112+
</para>
113+
</listitem>
114+
115+
<listitem>
116+
<para>
117+
Fix <application>pg_upgrade</> to correctly restore extension
118+
membership for operator families containing only one operator class
119+
(Tom Lane)
120+
</para>
121+
122+
<para>
123+
In such a case, the operator family was restored into the new database,
124+
but it was no longer marked as part of the extension. This had no
125+
immediate ill effects, but would cause later <application>pg_dump</>
126+
runs to emit output that would cause (harmless) errors on restore.
127+
</para>
128+
</listitem>
129+
130+
<listitem>
131+
<para>
132+
Back-port 9.4-era memory-barrier code changes into 9.2 and 9.3 (Tom Lane)
133+
</para>
134+
135+
<para>
136+
These changes were not originally needed in pre-9.4 branches, but we
137+
recently back-patched a fix that expected the barrier code to work
138+
properly. Only IA64 (when using icc), HPPA, and Alpha platforms are
139+
affected.
140+
</para>
141+
</listitem>
142+
143+
<listitem>
144+
<para>
145+
Reduce the number of SysV semaphores used by a build configured with
146+
<option>--disable-spinlocks</> (Tom Lane)
147+
</para>
148+
</listitem>
149+
150+
<listitem>
151+
<para>
152+
Rename internal function <function>strtoi()</>
153+
to <function>strtoint()</> to avoid conflict with a NetBSD library
154+
function (Thomas Munro)
155+
</para>
156+
</listitem>
157+
158+
<listitem>
159+
<para>
160+
Fix reporting of errors from <function>bind()</>
161+
and <function>listen()</> system calls on Windows (Tom Lane)
162+
</para>
163+
</listitem>
164+
165+
<listitem>
166+
<para>
167+
Reduce verbosity of compiler output when building with Microsoft Visual
168+
Studio (Christian Ullrich)
169+
</para>
170+
</listitem>
171+
172+
<listitem>
173+
<para>
174+
Avoid possibly-unsafe use of Windows' <function>FormatMessage()</>
175+
function (Christian Ullrich)
176+
</para>
177+
178+
<para>
179+
Use the <literal>FORMAT_MESSAGE_IGNORE_INSERTS</> flag where
180+
appropriate. No live bug is known to exist here, but it seems like a
181+
good idea to be careful.
182+
</para>
183+
</listitem>
184+
185+
<listitem>
186+
<para>
187+
Update time zone data files to <application>tzdata</> release 2016d
188+
for DST law changes in Russia and Venezuela. There are new zone
189+
names <literal>Europe/Kirov</> and <literal>Asia/Tomsk</> to reflect
190+
the fact that these regions now have different time zone histories from
191+
adjacent regions.
192+
</para>
193+
</listitem>
194+
195+
</itemizedlist>
196+
197+
</sect2>
198+
</sect1>
199+
4200
<sect1 id="release-9-2-16">
5201
<title>Release 9.2.16</title>
6202

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp