8000 Release notes for 9.6.5, 9.5.9, 9.4.14, 9.3.19, 9.2.23. · lelisa2016/postgres@bf0dcdb · GitHub
[go: up one dir, main page]
Skip to content

Commit bf0dcdb

Browse files
tglsfdctglsfdc
committed
Release notes for 9.6.5, 9.5.9, 9.4.14, 9.3.19, 9.2.23.
1 parent 8cda1fa commit bf0dcdb

File tree

1 file changed

+139
-0
lines changed

1 file changed

+139
-0
lines changed

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

Lines changed: 139 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,145 @@
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-23">
5+
<title>Release 9.2.23</title>
6+
7+
<formalpara>
8+
<title>Release date:</title>
9+
<para>2017-08-31</para>
10+
</formalpara>
11+
12+
<para>
13+
This release contains a small number of fixes from 9.2.22.
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.23</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+
Show foreign tables
46+
in <structname>information_schema</>.<structname>table_privileges</>
47+
view (Peter Eisentraut)
48+
</para>
49+
50+
<para>
51+
All other relevant <structname>information_schema</> views include
52+
foreign tables, but this one ignored them.
53+
</para>
54+
55+
<para>
56+
Since this view definition is installed by <application>initdb</>,
57+
merely upgrading will not fix the problem. If you need to fix this
58+
in an existing installation, you can, as a superuser, do this
59+
in <application>psql</>:
60+
<programlisting>
61+
BEGIN;
62+
DROP SCHEMA information_schema CASCADE;
63+
\i <replaceable>SHAREDIR</>/information_schema.sql
64+
COMMIT;
65+
</programlisting>
66+
(Run <literal>pg_config --sharedir</> if you're uncertain
67+
where <replaceable>SHAREDIR</> is.) This must be repeated in each
68+
database to be fixed.
69+
</para>
70+
</listitem>
71+
72+
<listitem>
73+
<para>
74+
Clean up handling of a fatal exit (e.g., due to receipt
75+
of <systemitem>SIGTERM</>) that occurs while trying to execute
76+
a <command>ROLLBACK</> of a failed transaction (Tom Lane)
77+
</para>
78+
79+
<para>
80+
This situation could result in an assertion failure. In production
81+
builds, the exit would still occur, but it would log an unexpected
82+
message about <quote>cannot drop active portal</>.
83+
</para>
84+
</listitem>
85+
86+
<listitem>
87+
<para>
88+
Remove assertion that could trigger during a fatal exit (Tom Lane)
89+
</para>
90+
</listitem>
91+
92+
<listitem>
93+
<para>
94+
Correctly identify columns that are of a range type or domain type over
95+
a composite type or domain type being searched for (Tom Lane)
96+
</para>
97+
98+
<para>
99+
Certain <command>ALTER</> commands that change the definition of a
100+
composite type or domain type are supposed to fail if there are any
101+
stored values of that type in the database, because they lack the
102+
infrastructure needed to update or check such values. Previously,
103+
these checks could miss relevant values that are wrapped inside range
104+
types or sub-domains, possibly allowing the database to become
105+
inconsistent.
106+
</para>
107+
</listitem>
108+
109+
<listitem>
110+
<para>
111+
Change <application>ecpg</>'s parser to allow <literal>RETURNING</>
112+
clauses without attached C variables (Michael Meskes)
113+
</para>
114+
115+
<para>
116+
This allows <application>ecpg</> programs to contain SQL constructs
117+
that use <literal>RETURNING</> internally (for example, inside a CTE)
118+
rather than using it to define values to be returned to the client.
119+
</para>
120+
</listitem>
121+
122+
<listitem>
123+
<para>
124+
Improve selection of compiler flags for PL/Perl on Windows (Tom Lane)
125+
</para>
126+
127+
<para>
128+
This fix avoids possible crashes of PL/Perl due to inconsistent
129+
assumptions about the width of <type>time_t</> values.
130+
A side-effect that may be visible to extension developers is
131+
that <literal>_USE_32BIT_TIME_T</> is no longer defined globally
132+
in <productname>PostgreSQL</> Windows builds. This is not expected
133+
to cause problems, because type <type>time_t</> is not used
134+
in any <productname>PostgreSQL</> API definitions.
135+
</para>
136+
</listitem>
137+
138+
</itemizedlist>
139+
140+
</sect2>
141+
</sect1>
142+
4143
<sect1 id="release-9-2-22">
5144
<title>Release 9.2.22</title>
6145

0 commit comments

Comments
 (0)
0