Skip to content

Commit 50714dd

Browse files
tglsfdctglsfdc
committed
Release notes for 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, 9.2.24.
In the v10 branch, also back-patch the effects of 1ff01b3 and c29c578 on these files, to reduce future maintenance issues. (I'd do it further back, except that the 9.X branches differ anyway due to xlog-to-wal link tag renaming.)
1 parent 13406fe commit 50714dd

File tree

1 file changed

+176
-0
lines changed

1 file changed

+176
-0
lines changed

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

Lines changed: 176 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,182 @@
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-24">
5+
<title>Release 9.2.24</title>
6+
7+
<formalpara>
8+
<title>Release date:</title>
9+
<para>2017-11-09</para>
10+
</formalpara>
11+
12+
<para>
13+
This release contains a variety of fixes from 9.2.23.
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+
This is expected to be the last <productname>PostgreSQL</productname>
20+
release in the 9.2.X series. Users are encouraged to update to a newer
21+
release branch soon.
22+
</para>
23+
24+
<sect2>
25+
<title>Migration to Version 9.2.24</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.22,
33+
see <xref linkend="release-9-2-22">.
34+
</para>
35+
36+
</sect2>
37+
38+
<sect2>
39+
<title>Changes</title>
40+
41+
<itemizedlist>
42+
43+
<listitem>
44+
<para>
45+
Properly reject attempts to convert infinite float values to
46+
type <type>numeric</type> (Tom Lane, KaiGai Kohei)
47+
</para>
48+
49+
<para>
50+
Previously the behavior was platform-dependent.
51+
</para>
52+
</listitem>
53+
54+
<listitem>
55+
<para>
56+
Fix corner-case crashes when columns have been added to the end of a
57+
view (Tom Lane)
58+
</para>
59+
</listitem>
60+
61+
<listitem>
62+
<para>
63+
Record proper dependencies when a view or rule
64+
contains <structname>FieldSelect</structname>
65+
or <structname>FieldStore</structname> expression nodes (Tom Lane)
66+
</para>
67+
68+
<para>
69+
Lack of these dependencies could allow a column or data
70+
type <command>DROP</command> to go through when it ought to fail,
71+
thereby causing later uses of the view or rule to get errors.
72+
This patch does not do anything to protect existing views/rules,
73+
only ones created in the future.
74+
</para>
75+
</listitem>
76+
77+
<listitem>
78+
<para>
79+
Correctly detect hashability of range data types (Tom Lane)
80+
</para>
81+
82+
<para>
83+
The planner mistakenly assumed that any range type could be hashed
84+
for use in hash joins or hash aggregation, but actually it must check
85+
whether the range's subtype has hash support. This does not affect any
86+
of the built-in range types, since they're all hashable anyway.
87+
</para>
88+
</listitem>
89+
90+
<listitem>
91+
<para>
92+
Fix low-probability loss of <command>NOTIFY</command> messages due to
93+
XID wraparound (Marko Tiikkaja, Tom Lane)
94+
</para>
95+
96+
<para>
97+
If a session executed no queries, but merely listened for
98+
notifications, for more than 2 billion transactions, it started to miss
99+
some notifications from concurrently-committing transactions.
100+
</para>
101+
</listitem>
102+
103+
<listitem>
104+
<para>
105+
Prevent low-probability crash in processing of nested trigger firings
106+
(Tom Lane)
107+
</para>
108+
</listitem>
109+
110+
<listitem>
111+
<para>
112+
Correctly restore the umask setting when file creation fails
113+
in <command>COPY</command> or <function>lo_export()</function>
114+
(Peter Eisentraut)
115+
</para>
116+
</listitem>
117+
118+
<listitem>
119+
<para>
120+
Give a better error message for duplicate column names
121+
in <command>ANALYZE</command> (Nathan Bossart)
122+
</para>
123+
</listitem>
124+
125+
<listitem>
126+
<para>
127+
Fix <application>libpq</application> to not require user's home
128+
directory to exist (Tom Lane)
129+
</para>
130+
131+
<para>
132+
In v10, failure to find the home directory while trying to
133+
read <filename>~/.pgpass</filename> was treated as a hard error,
134+
but it should just cause that file to not be found. Both v10 and
135+
previous release branches made the same mistake when
136+
reading <filename>~/.pg_service.conf</filename>, though this was less
137+
obvious since that file is not sought unless a service name is
138+
specified.
139+
</para>
140+
</listitem>
141+
142+
<listitem>
143+
<para>
144+
Fix <application>libpq</application> to guard against integer
145+
overflow in the row count of a <structname>PGresult</structname>
146+
(Michael Paquier)
147+
</para>
148+
</listitem>
149+
150+
<listitem>
151+
<para>
152+
Sync our copy of the timezone library with IANA release tzcode2017c
153+
(Tom Lane)
154+
</para>
155+
156+
<para>
157+
This fixes various issues; the only one likely to be user-visible
158+
is that the default DST rules for a POSIX-style zone name, if
159+
no <filename>posixrules</filename> file exists in the timezone data
160+
directory, now match current US law rather than what it was a dozen
161+
years ago.
162+
</para>
163+
</listitem>
164+
165+
<listitem>
166+
<para>
167+
Update time zone data files to <application>tzdata</application>
168+
release 2017c for DST law changes in Fiji, Namibia, Northern Cyprus,
169+
Sudan, Tonga, and Turks &amp; Caicos Islands, plus historical
170+
corrections for Alaska, Apia, Burma, Calcutta, Detroit, Ireland,
171+
Namibia, and Pago Pago.
172+
</para>
173+
</listitem>
174+
175+
</itemizedlist>
176+
177+
</sect2>
178+
</sect1>
179+
4180
<sect1 id="release-9-2-23">
5181
<title>Release 9.2.23</title>
6182

0 commit comments

Comments
 (0)