8000 Update release notes for 9.3.2, 9.2.6, 9.1.11, 9.0.15, 8.4.19. · xiaom/postgres@45f0620 · GitHub
[go: up one dir, main page]
Skip to content

Commit 45f0620

Browse files
tglsfdctglsfdc
committed
Update release notes for 9.3.2, 9.2.6, 9.1.11, 9.0.15, 8.4.19.
1 parent 0176f8b commit 45f0620

File tree

3 files changed

+783
-62
lines changed

3 files changed

+783
-62
lines changed

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

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

4+
<sect1 id="release-8-4-19">
5+
<title>Release 8.4.19</title>
6+
7+
<note>
8+
<title>Release Date</title>
9+
<simpara>2013-12-05</simpara>
10+
</note>
11+
12+
<para>
13+
This release contains a variety of fixes from 8.4.18.
14+
For information about new features in the 8.4 major release, see
15+
<xref linkend="release-8-4">.
16+
</para>
17+
18+
<sect2>
19+
<title>Migration to Version 8.4.19</title>
20+
21+
<para>
22+
A dump/restore is not required for those running 8.4.X.
23+
</para>
24+
25+
<para>
26+
However, this release corrects a potential data corruption
27+
issue. See the first changelog entry below to find out whether
28+
your installation has been affected and what steps you can take if so.
29+
</para>
30+
31+
<para>
32+
Also, if you are upgrading from a version earlier than 8.4.17,
33+
see the release notes for 8.4.17.
34+
</para>
35+
36+
</sect2>
37+
38+
<sect2>
39+
<title>Changes</title>
40+
41+
<itemizedlist>
42+
43+
<listitem>
44+
<para>
45+
Fix <command>VACUUM</>'s tests to see whether it can
46+
update <structfield>relfrozenxid</> (Andres Freund)
47+
</para>
48+
49+
<para>
50+
In some cases <command>VACUUM</> (either manual or autovacuum) could
51+
incorrectly advance a table's <structfield>relfrozenxid</> value,
52+
allowing tuples to escape freezing, causing those rows to become
53+
invisible once 2^31 transactions have elapsed. The probability of
54+
data loss is fairly low since multiple incorrect advancements would
55+
need to happen before actual loss occurs, but it's not zero. Users
56+
upgrading from release 8.4.8 or earlier are not affected, but all later
57+
versions contain the bug.
58+
</para>
59+
60+
<para>
61+
The issue can be ameliorated by, after upgrading, vacuuming all tables
62+
in all databases while having <link
63+
linkend="guc-vacuum-freeze-table-age"><varname>vacuum_freeze_table_age</></link>
64+
set to zero. This will fix any latent corruption but will not be able
65+
to fix all pre-existing data errors. However, an installation can be
66+
presumed safe after performing this vacuuming if it has executed fewer
67+
than 2^31 update transactions in its lifetime (check this with
68+
<literal>SELECT txid_current() < 2^31</>).
69+
</para>
70+
</listitem>
71+
72+
<listitem>
73+
<para>
74+
Fix race condition in GIN index posting tree page deletion (Heikki
75+
Linnakangas)
76+
</para>
77+
78+
<para>
79+
This could lead to transient wrong answers or query failures.
80+
</para>
81+
</listitem>
82+
83+
<listitem>
84+
<para>
85+
Avoid flattening a subquery whose <literal>SELECT</> list contains a
86+
volatile function wrapped inside a sub-<literal>SELECT</> (Tom Lane)
87+
</para>
88+
89+
<para>
90+
This avoids unexpected results due to extra evaluations of the
91+
volatile function.
92+
</para>
93+
</listitem>
94+
95+
<listitem>
96+
<para>
97+
Fix planner's processing of non-simple-variable subquery outputs
98+
nested within outer joins (Tom Lane)
99+
</para>
100+
101+
<para>
102+
This error could lead to incorrect plans for queries involving
103+
multiple levels of subqueries within <literal>JOIN</> syntax.
104+
</para>
105+
</listitem>
106+
107+
<listitem>
108+
<para>
109+
Fix premature deletion of temporary files (Andres Freund)
110+
</para>
111+
</listitem>
112+
113+
<listitem>
114+
<para>
115+
Fix possible read past end of memory in rule printing (Peter Eisentraut)
116+
</para>
117+
</listitem>
118+
119+
<listitem>
120+
<para>
121+
Fix array slicing of <type>int2vector</> and <type>oidvector</> values
122+
(Tom Lane)
123+
</para>
124+
125+
<para>
126+
Expressions of this kind are now implicitly promoted to
127+
regular <type>int2</> or <type>oid</> arrays.
128+
</para>
129+
</listitem>
130+
131+
<listitem>
132+
<para>
133+
Fix incorrect behaviors when using a SQL-standard, simple GMT offset
134+
timezone (Tom Lane)
135+
</para>
136+
137+
<para>
138+
In some cases, the system would use the simple GMT offset value when
139+
it should have used the regular timezone setting that had prevailed
140+
before the simple offset was selected. This change also causes
141+
the <function>timeofday</> function to honor the simple GMT offset
142+
zone.
143+
</para>
144+
</listitem>
145+
146+
<listitem>
147+
<para>
148+
Prevent possible misbehavior when logging translations of Windows
149+
error codes (Tom Lane)
150+
</para>
151+
</listitem>
152+
153+
<listitem>
154+
<para>
155+
Properly quote generated command lines in <application>pg_ctl</>
156+
(Naoya Anzai and Tom Lane)
157+
</para>
158+
159+
<para>
160+
This fix applies only to Windows.
161+
</para>
162+
</listitem>
163+
164+
<listitem>
165+
<para>
166+
Fix <application>pg_dumpall</> to work when a source database
167+
sets <link
168+
linkend="guc-default-transaction-read-only"><varname>default_transaction_read_only</></link>
169+
via <command>ALTER DATABASE SET</> (Kevin Grittner)
170+
</para>
171+
172+
<para>
173+
Previously, the generated script would fail during restore.
174+
</para>
175+
</listitem>
176+
177+
<listitem>
178+
<para>
179+
Fix <application>ecpg</>'s processing of lists of variables
180+
declared <type>varchar</> (Zolt&aacute;n B&ouml;sz&ouml;rm&eacute;nyi)
181+
</para>
182+
</listitem>
183+
184+
<listitem>
185+
<para>
186+
Make <filename>contrib/lo</> defend against incorrect trigger definitions
187+
(Marc Cousin)
188+
</para>
189+
</listitem>
190+
191+
<listitem>
192+
<para>
193+
Update time zone data files to <application>tzdata</> release 2013h
194+
for DST law changes in Argentina, Brazil, Jordan, Libya,
195+
Liechtenstein, Morocco, and Palestine. Also, new timezone
196+
abbreviations WIB, WIT, WITA for Indonesia.
197+
</para>
198+
</listitem>
199+
200+
</itemizedlist>
201+
202+
</sect2>
203+
</sect1>
204+
4205
<sect1 id="release-8-4-18">
5206
<title>Release 8.4.18</title>
6207

@@ -23,8 +224,8 @@
23224
</para>
24225

25226
<para>
26-
Also, if you are upgrading from a version earlier than 8.4.10,
27-
see the release notes for 8.4.10.
227+
However, if you are upgrading from a version earlier than 8.4.17,
228+
see the release notes for 8.4.17.
28229
</para>
29230

30231
</sect2>
@@ -36,12 +237,13 @@
36237

37238
<listitem>
38239
<para>
39-
Prevent downcasing of non-ASCII non-double-quoted identifiers in
40-
multi-byte encodings (Andrew Dunstan)
240+
Prevent corruption of multi-byte characters when attempting to
241+
case-fold identifiers (Andrew Dunstan)
41242
</para>
42243

43244
<para>
44-
The previous behavior was wrong and confusing.
245+
<productname>PostgreSQL</> case-folds non-ASCII characters only
246+
when using a single-byte server encoding.
45247
</para>
46248
</listitem>
47249

@@ -61,7 +263,7 @@
61263

62264
<listitem>
63265
<para>
64-
Fix libpq SSL deadlock bug (Stephen Frost)
266+
Fix deadlock bug in libpq when using SSL (Stephen Frost)
65267
</para>
66268
</listitem>
67269

@@ -85,21 +287,24 @@
85287
</para>
86288

87289
<para>
88-
Previously such push downs could generate errors.
290+
Subqueries of a <literal>UNION</> or <literal>INTERSECT</> that
291+
contain set-returning functions or volatile functions in their
292+
<literal>SELECT</> lists could be improperly optimized, leading to
293+
run-time errors or incorrect query results.
89294
</para>
90295
</listitem>
91296

92297
<listitem>
93298
<para>
94-
Fix rare <literal>GROUP BY</> query error caused by improperly
95-
processed data type modifiers (Tom Lane)
299+
Fix rare case of <quote>failed to locate grouping columns</>
300+
planner failure (Tom Lane)
96301
</para>
97302
</listitem>
98303

99304
<listitem>
100305
<para>
101-
Allow view dump code to better handle dropped columns on base tables
102-
(Tom Lane)
306+
Improve view dumping code's handling of dropped columns in referenced
307+
tables (Tom Lane)
103308
</para>
104309
</listitem>
105310

@@ -164,12 +369,16 @@
164369

165370
<listitem>
166371
<para>
167-
Allow various spellings of infinity on all platforms (Tom Lane)
372+
Ensure that floating-point data input accepts standard spellings
373+
of <quote>infinity</> on all platforms (Tom Lane)
168374
</para>
169375

170376
<para>
171-
Supported infinity values are "inf", "+inf", "-inf", "infinity",
172-
"+infinity", and "-infinity".
377+
The C99 standard says that allowable spellings are <literal>inf</>,
378+
<literal>+inf</>, <literal>-inf</>, <literal>infinity</>,
379+
<literal>+infinity</>, and <literal>-infinity</>. Make sure we
380+
recognize these even if the platform's <function>strtod</> function
381+
doesn't.
173382
</para>
174383
</listitem>
175384

@@ -183,9 +392,8 @@
183392
<listitem>
184393
<para>
185394
Update time zone data files to <application>tzdata</> release 2013d
186-
for DST law changes in DST law changes in Israel, Morocco, Palestine,
187-
Paraguay. Also, historical zone data corrections for Macquarie Island
188-
(Tom Lane)
395+
for DST law changes in Israel, Morocco, Palestine, and Paraguay.
396+
Also, historical zone data corrections for Macquarie Island.
189397
</para>
190398
</listitem>
191399

0 commit comments

Comments
 (0)
0