Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 3178f46

Browse files
tglsfdctglsfdc
committed
Release notes for 9.6.3, 9.5.7, 9.4.12, 9.3.17, 9.2.21.
1 parent fab2d0d commit 3178f46

File tree

5 files changed

+2551
-2
lines changed

5 files changed

+2551
-2
lines changed

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

+325
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,331 @@
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-21">
5+
<title>Release 9.2.21</title>
6+
7+
<note>
8+
<title>Release Date</title>
9+
<simpara>2017-05-11</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a variety of fixes from 9.2.20.
14+
For information about new features in the 9.2 major release, see
15+
<xref linkend="release-9-2">.
16+
</para>
17+
18+
<para>
19+
The <productname>PostgreSQL</> community will stop releasing updates
20+
for the 9.2.X release series in September 2017.
21+
Users are encouraged to update to a newer release branch soon.
22+
</para>
23+
24+
<sect2>
25+
<title>Migration to Version 9.2.21</title>
26+
27+
<para>
28+
A dump/restore is not required for those running 9.2.X.
29+
</para>
30+
31+
<para>
32+
However, if you are upgrading from a version earlier than 9.2.20,
33+
see <xref linkend="release-9-2-20">.
34+
</para>
35+
36+
</sect2>
37+
38+
<sect2>
39+
<title>Changes</title>
40+
41+
<itemizedlist>
42+
43+
<listitem>
44+
<para>
45+
Fix possible corruption of <quote>init forks</> of unlogged indexes
46+
(Robert Haas, Michael Paquier)
47+
</para>
48+
49+
<para>
50+
This could result in an unlogged index being set to an invalid state
51+
after a crash and restart. Such a problem would persist until the
52+
index was dropped and rebuilt.
53+
</para>
54+
</listitem>
55+
56+
<listitem>
57+
<para>
58+
Fix incorrect reconstruction of <structname>pg_subtrans</> entries
59+
when a standby server replays a prepared but uncommitted two-phase
60+
transaction (Tom Lane)
61+
</para>
62+
63+
<para>
64+
In most cases this turned out to have no visible ill effects, but in
65+
corner cases it could result in circular references
66+
in <structname>pg_subtrans</>, potentially causing infinite loops
67+
in queries that examine rows modified by the two-phase transaction.
68+
</para>
69+
</listitem>
70+
71+
<listitem>
72+
<para>
73+
Ensure parsing of queries in extension scripts sees the results of
74+
immediately-preceding DDL (Julien Rouhaud, Tom Lane)
75+
</para>
76+
77+
<para>
78+
Due to lack of a cache flush step between commands in an extension
79+
script file, non-utility queries might not see the effects of an
80+
immediately preceding catalog change, such as <command>ALTER TABLE
81+
... RENAME</>.
82+
</para>
83+
</listitem>
84+
85+
<listitem>
86+
<para>
87+
Skip tablespace privilege checks when <command>ALTER TABLE ... ALTER
88+
COLUMN TYPE</> rebuilds an existing index (Noah Misch)
89+
</para>
90+
91+
<para>
92+
The command failed if the calling user did not currently have
93+
<literal>CREATE</> privilege for the tablespace containing the index.
94+
That behavior seems unhelpful, so skip the check, allowing the
95+
index to be rebuilt where it is.
96+
</para>
97+
</listitem>
98+
99+
<listitem>
100+
<para>
101+
Fix <command>ALTER TABLE ... VALIDATE CONSTRAINT</> to not recurse
102+
to child tables when the constraint is marked <literal>NO INHERIT</>
103+
(Amit Langote)
104+
</para>
105+
106+
<para>
107+
This fix prevents unwanted <quote>constraint does not exist</> failures
108+
when no matching constraint is present in the child tables.
109+
</para>
110+
</listitem>
111+
112+
<listitem>
113+
<para>
114+
Fix <command>VACUUM</> to account properly for pages that could not
115+
be scanned due to conflicting page pins (Andrew Gierth)
116+
</para>
117+
118+
<para>
119+
This tended to lead to underestimation of the number of tuples in
120+
the table. In the worst case of a small heavily-contended
121+
table, <command>VACUUM</> could incorrectly report that the table
122+
contained no tuples, leading to very bad planning choices.
123+
</para>
124+
</listitem>
125+
126+
<listitem>
127+
<para>
128+
Ensure that bulk-tuple-transfer loops within a hash join are
129+
interruptible by query cancel requests (Tom Lane, Thomas Munro)
130+
</para>
131+
</listitem>
132+
133+
<listitem>
134+
<para>
135+
Fix <function>cursor_to_xml()</> to produce valid output
136+
with <replaceable>tableforest</> = false
137+
(Thomas Munro, Peter Eisentraut)
138+
</para>
139+
140+
<para>
141+
Previously it failed to produce a wrapping <literal>&lt;table&gt;</>
142+
element.
143+
</para>
144+
</listitem>
145+
146+
<listitem>
147+
<para>
148+
Improve performance of <structname>pg_timezone_names</> view
149+
(Tom Lane, David Rowley)
150+
</para>
151+
</listitem>
152+
153+
<listitem>
154+
<para>
155+
Fix sloppy handling of corner-case errors from <function>lseek()</>
156+
and <function>close()</> (Tom Lane)
157+
</para>
158+
159+
<para>
160+
Neither of these system calls are likely to fail in typical situations,
161+
but if they did, <filename>fd.c</> could get quite confused.
162+
</para>
163+
</listitem>
164+
165+
<listitem>
166+
<para>
167+
Fix incorrect check for whether postmaster is running as a Windows
168+
service (Michael Paquier)
169+
</para>
170+
171+
<para>
172+
This could result in attempting to write to the event log when that
173+
isn't accessible, so that no logging happens at all.
174+
</para>
175+
</listitem>
176+
177+
<listitem>
178+
<para>
179+
Fix <application>ecpg</> to support <command>COMMIT PREPARED</>
180+
and <command>ROLLBACK PREPARED</> (Masahiko Sawada)
181+
</para>
182+
</listitem>
183+
184+
<listitem>
185+
<para>
186+
Fix a double-free error when processing dollar-quoted string literals
187+
in <application>ecpg</> (Michael Meskes)
188+
</para>
189+
</listitem>
190+
191+
<listitem>
192+
<para>
193+
In <application>pg_dump</>, fix incorrect schema and owner marking for
194+
comments and security labels of some types of database objects
195+
(Giuseppe Broccolo, Tom Lane)
196+
</para>
197+
198+
<para>
199+
In simple cases this caused no ill effects; but for example, a
200+
schema-selective restore might omit comments it should include, because
201+
they were not marked as belonging to the schema of their associated
202+
object.
203+
</para>
204+
</listitem>
205+
206+
<listitem>
207+
<para>
208+
Avoid emitting an invalid list file in <literal>pg_restore -l</>
209+
when SQL object names contain newlines (Tom Lane)
210+
</para>
211+
212+
<para>
213+
Replace newlines by spaces, which is sufficient to make the output
214+
valid for <literal>pg_restore -L</>'s purposes.
215+
</para>
216+
</listitem>
217+
218+
<listitem>
219+
<para>
220+
Fix <application>pg_upgrade</> to transfer comments and security labels
221+
attached to <quote>large objects</> (blobs) (Stephen Frost)
222+
</para>
223+
224+
<para>
225+
Previously, blobs were correctly transferred to the new database, but
226+
any comments or security labels attached to them were lost.
227+
</para>
228+
</listitem>
229+
230+
<listitem>
231+
<para>
232+
Improve error handling
233+
in <filename>contrib/adminpack</>'s <function>pg_file_write()</>
234+
function (Noah Misch)
235+
</para>
236+
237+
<para>
238+
Notably, it failed to detect errors reported
239+
by <function>fclose()</>.
240+
</para>
241+
</listitem>
242+
243+
<listitem>
244+
<para>
245+
In <filename>contrib/dblink</>, avoid leaking the previous unnamed
246+
connection when establishing a new unnamed connection (Joe Conway)
247+
</para>
248+
</listitem>
249+
250+
<listitem>
251+
<para>
252+
Support OpenSSL 1.1.0 (Heikki Linnakangas, Andreas Karlsson, Tom Lane)
253+
</para>
254+
255+
<para>
256+
This is a back-patch of work previously done in newer branches;
257+
it's needed since many platforms are adopting newer OpenSSL versions.
258+
</para>
259+
</listitem>
260+
261+
<listitem>
262+
<para>
263+
Support Tcl 8.6 in MSVC builds (&Aacute;lvaro Herrera)
264+
</para>
265+
</listitem>
266+
267+
<listitem>
268+
<para>
269+
Sync our copy of the timezone library with IANA release tzcode2017b
270+
(Tom Lane)
271+
</para>
272+
273+
<para>
274+
This fixes a bug affecting some DST transitions in January 2038.
275+
</para>
276+
</listitem>
277+
278+
<listitem>
279+
<para>
280+
Update time zone data files to <application>tzdata</> release 2017b
281+
for DST law changes in Chile, Haiti, and Mongolia, plus historical
282+
corrections for Ecuador, Kazakhstan, Liberia, and Spain.
283+
Switch to numeric abbreviations for numerous time zones in South
284+
America, the Pacific and Indian oceans, and some Asian and Middle
285+
Eastern countries.
286+
</para>
287+
288+
<para>
289+
The IANA time zone database previously provided textual abbreviations
290+
for all time zones, sometimes making up abbreviations that have little
291+
or no currency among the local population. They are in process of
292+
reversing that policy in favor of using numeric UTC offsets in zones
293+
where there is no evidence of real-world use of an English
294+
abbreviation. At least for the time being, <productname>PostgreSQL</>
295+
will continue to accept such removed abbreviations for timestamp input.
296+
But they will not be shown in the <structname>pg_timezone_names</>
297+
view nor used for output.
298+
</para>
299+
</listitem>
300+
301+
<listitem>
302+
<para>
303+
Use correct daylight-savings rules for POSIX-style time zone names
304+
in MSVC builds (David Rowley)
305+
</para>
306+
307+
<para>
308+
The Microsoft MSVC build scripts neglected to install
309+
the <filename>posixrules</> file in the timezone directory tree.
310+
This resulted in the timezone code falling back to its built-in
311+
rule about what DST behavior to assume for a POSIX-style time zone
312+
name. For historical reasons that still corresponds to the DST rules
313+
the USA was using before 2007 (i.e., change on first Sunday in April
314+
and last Sunday in October). With this fix, a POSIX-style zone name
315+
will use the current and historical DST transition dates of
316+
the <literal>US/Eastern</> zone. If you don't want that, remove
317+
the <filename>posixrules</> file, or replace it with a copy of some
318+
other zone file (see <xref linkend="datatype-timezones">). Note that
319+
due to caching, you may need to restart the server to get such changes
320+
to take effect.
321+
</para>
322+
</listitem>
323+
324+
</itemizedlist>
325+
326+
</sect2>
327+
</sect1>
328+
4329
<sect1 id="release-9-2-20">
5330
<title>Release 9.2.20</title>
6331

0 commit comments

Comments
 (0)