10000 Release notes for 10.3, 9.6.8, 9.5.12, 9.4.17, 9.3.22. · divag711/postgres@aa246ee · GitHub
[go: up one dir, main page]
Skip to content

Commit aa246ee

Browse files
tglsfdctglsfdc
committed
Release notes for 10.3, 9.6.8, 9.5.12, 9.4.17, 9.3.22.
1 parent a7a6051 commit aa246ee

File tree

1 file changed

+112
-0
lines changed

1 file changed

+112
-0
lines changed

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

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

4+
<sect1 id="release-9-3-22">
5+
<title>Release 9.3.22</title>
6+
7+
<formalpara>
8+
<title>Release date:</title>
9+
<para>2018-03-01</para>
10+
</formalpara>
11+
12+
<para>
13+
This release contains a variety of fixes from 9.3.21.
14+
For information about new features in the 9.3 major release, see
15+
<xref linkend=&qu 10000 ot;release-9-3">.
16+
</para>
17+
18+
<sect2>
19+
<title>Migration to Version 9.3.22</title>
20+
21+
<para>
22+
A dump/restore is not required for those running 9.3.X.
23+
</para>
24+
25+
<para>
26+
However, if you are upgrading from a version earlier than 9.3.18,
27+
see <xref linkend="release-9-3-18">.
28+
</para>
29+
</sect2>
30+
31+
<sect2>
32+
<title>Changes</title>
33+
34+
<itemizedlist>
35+
36+
<listitem>
37+
<para>
38+
Fix misbehavior of concurrent-update rechecks with CTE references
39+
appearing in subplans (Tom Lane)
40+
</para>
41+
42+
<para>
43+
If a CTE (<literal>WITH</literal> clause reference) is used in an
44+
InitPlan or SubPlan, and the query requires a recheck due to trying
45+
to update or lock a concurrently-updated row, incorrect results could
46+
be obtained.
47+
</para>
48+
</listitem>
49+
50+
<listitem>
51+
<para>
52+
Fix planner failures with overlapping mergejoin clauses in an outer
53+
join (Tom Lane)
54+
</para>
55+
56+
<para>
57+
These mistakes led to <quote>left and right pathkeys do not match in
58+
mergejoin</quote> or <quote>outer pathkeys do not match
59+
mergeclauses</quote> planner errors in corner cases.
60+
</para>
61+
</listitem>
62+
63+
<listitem>
64+
<para>
65+
Repair <application>pg_upgrade</application>'s failure to
66+
preserve <structfield>relfrozenxid</structfield> for materialized
67+
views (Tom Lane, Andres Freund)
68+
</para>
69+
70+
<para>
71+
This oversight could lead to data corruption in materialized views
72+
after an upgrade, manifesting as <quote>could not access status of
73+
transaction</quote> or <quote>found xmin from before
74+
relfrozenxid</quote> errors. The problem would be more likely to
75+
occur in seldom-refreshed materialized views, or ones that were
76+
maintained only with <command>REFRESH MATERIALIZED VIEW
77+
CONCURRENTLY</command>.
78+
</para>
79+
80+
<para>
81+
If such corruption is observed, it can be repaired by refreshing the
82+
materialized view (without <literal>CONCURRENTLY</literal>).
83+
</para>
84+
</listitem>
85+
86+
<listitem>
87+
<para>
88+
Fix incorrect reporting of PL/Python function names in
89+
error <literal>CONTEXT</literal> stacks (Tom Lane)
90+
</para>
91+
92+
<para>
93+
An error occurring within a nested PL/Python function call (that is,
94+
one reached via a SPI query from another PL/Python function) would
95+
result in a stack trace showing the inner function's name twice,
96+
rather than the expected results. Also, an error in a nested
97+
PL/Python <literal>DO</literal> block could result in a null pointer
98+
dereference crash on some platforms.
99+
</para>
100+
</listitem>
101+
102+
<listitem>
103+
<para>
104+
Allow <filename>contrib/auto_explain</filename>'s
105+
<varname>log_min_duration</varname> setting to range up
106+
to <literal>INT_MAX</literal>, or about 24 days instead of 35 minutes
107+
(Tom Lane)
108+
</para>
109+
</listitem>
110+
111+
</itemizedlist>
112+
113+
</sect2>
114+
</sect1>
115+
4116
<sect1 id="release-9-3-21">
5117
<title>Release 9.3.21</title>
6118

0 commit comments

Comments
 (0)
0