database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-25 21:42:33 +03:00
Code

Release notes for 9.6.5, 9.5.9, 9.4.14, 9.3.19, 9.2.23.

Browse Source
This commit is contained in:
Tom Lane 2017-08-27 17:35:04 -04:00
parent 6a5366e69a
commit f97c55c708
5 changed files with 581 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

139
doc/src/sgml/release-9.2.sgml
View File

@ -1,6 +1,145 @@
<!-- doc/src/sgml/release-9.2.sgml -->
<!-- See header comment in release.sgml about typical markup -->
<sect1 id="release-9-2-23">
<title>Release 9.2.23</title>
<formalpara>
<title>Release date:</title>
<para>2017-08-31</para>
</formalpara>
<para>
This release contains a small number of fixes from 9.2.22.
For information about new features in the 9.2 major release, see
<xref linkend="release-9-2">.
</para>
<para>
The <productname>PostgreSQL</> community will stop releasing updates
for the 9.2.X release series in September 2017.
Users are encouraged to update to a newer release branch soon.
</para>
<sect2>
<title>Migration to Version 9.2.23</title>
<para>
A dump/restore is not required for those running 9.2.X.
</para>
<para>
However, if you are upgrading from a version earlier than 9.2.22,
see <xref linkend="release-9-2-22">.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem>
<para>
Show foreign tables
in <structname>information_schema</>.<structname>table_privileges</>
view (Peter Eisentraut)
</para>
<para>
All other relevant <structname>information_schema</> views include
foreign tables, but this one ignored them.
</para>
<para>
Since this view definition is installed by <application>initdb</>,
merely upgrading will not fix the problem. If you need to fix this
in an existing installation, you can, as a superuser, do this
in <application>psql</>:
<programlisting>
BEGIN;
DROP SCHEMA information_schema CASCADE;
\i <replaceable>SHAREDIR</>/information_schema.sql
COMMIT;
</programlisting>
(Run <literal>pg_config --sharedir</> if you're uncertain
where <replaceable>SHAREDIR</> is.) This must be repeated in each
database to be fixed.
</para>
</listitem>
<listitem>
<para>
Clean up handling of a fatal exit (e.g., due to receipt
of <systemitem>SIGTERM</>) that occurs while trying to execute
a <command>ROLLBACK</> of a failed transaction (Tom Lane)
</para>
<para>
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
message about <quote>cannot drop active portal</>.
</para>
</listitem>
<listitem>
<para>
Remove assertion that could trigger during a fatal exit (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Correctly identify columns that are of a range type or domain type over
a composite type or domain type being searched for (Tom Lane)
</para>
<para>
Certain <command>ALTER</> commands that change the definition of a
composite type or domain type are supposed to fail if there are any
stored values of that type in the database, because they lack the
infrastructure needed to update or check such values. Previously,
these checks could miss relevant values that are wrapped inside range
types or sub-domains, possibly allowing the database to become
inconsistent.
</para>
</listitem>
<listitem>
<para>
Change <application>ecpg</>'s parser to allow <literal>RETURNING</>
clauses without attached C variables (Michael Meskes)
</para>
<para>
This allows <application>ecpg</> programs to contain SQL constructs
that use <literal>RETURNING</> internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
</para>
</listitem>
<listitem>
<para>
Improve selection of compiler flags for PL/Perl on Windows (Tom Lane)
</para>
<para>
This fix avoids possible crashes of PL/Perl due to inconsistent
assumptions about the width of <type>time_t</> values.
A side-effect that may be visible to extension developers is
that <literal>_USE_32BIT_TIME_T</> is no longer defined globally
in <productname>PostgreSQL</> Windows builds. This is not expected
to cause problems, because type <type>time_t</> is not used
in any <productname>PostgreSQL</> API definitions.
</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-9-2-22">
<title>Release 9.2.22</title>

140
doc/src/sgml/release-9.3.sgml
View File

@ -1,6 +1,146 @@
<!-- doc/src/sgml/release-9.3.sgml -->
<!-- See header comment in release.sgml about typical markup -->
<sect1 id="release-9-3-19">
<title>Release 9.3.19</title>
<formalpara>
<title>Release date:</title>
<para>2017-08-31</para>
</formalpara>
<para>
This release contains a small number of fixes from 9.3.18.
For information about new features in the 9.3 major release, see
<xref linkend="release-9-3">.
</para>
<sect2>
<title>Migration to Version 9.3.19</title>
<para>
A dump/restore is not required for those running 9.3.X.
</para>
<para>
However, if you are upgrading from a version earlier than 9.3.18,
see <xref linkend="release-9-3-18">.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem>
<para>
Show foreign tables
in <structname>information_schema</>.<structname>table_privileges</>
view (Peter Eisentraut)
</para>
<para>
All other relevant <structname>information_schema</> views include
foreign tables, but this one ignored them.
</para>
<para>
Since this view definition is installed by <application>initdb</>,
merely upgrading will not fix the problem. If you need to fix this
in an existing installation, you can, as a superuser, do this
in <application>psql</>:
<programlisting>
BEGIN;
DROP SCHEMA information_schema CASCADE;
\i <replaceable>SHAREDIR</>/information_schema.sql
COMMIT;
</programlisting>
(Run <literal>pg_config --sharedir</> if you're uncertain
where <replaceable>SHAREDIR</> is.) This must be repeated in each
database to be fixed.
</para>
</listitem>
<listitem>
<para>
Clean up handling of a fatal exit (e.g., due to receipt
of <systemitem>SIGTERM</>) that occurs while trying to execute
a <command>ROLLBACK</> of a failed transaction (Tom Lane)
</para>
<para>
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
message about <quote>cannot drop active portal</>.
</para>
</listitem>
<listitem>
<para>
Remove assertion that could trigger during a fatal exit (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Correctly identify columns that are of a range type or domain type over
a composite type or domain type being searched for (Tom Lane)
</para>
<para>
Certain <command>ALTER</> commands that change the definition of a
composite type or domain type are supposed to fail if there are any
stored values of that type in the database, because they lack the
infrastructure needed to update or check such values. Previously,
these checks could miss relevant values that are wrapped inside range
types or sub-domains, possibly allowing the database to become
inconsistent.
</para>
</listitem>
<listitem>
<para>
Fix crash in <application>pg_restore</> when using parallel mode and
using a list file to select a subset of items to restore (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Change <application>ecpg</>'s parser to allow <literal>RETURNING</>
clauses without attached C variables (Michael Meskes)
</para>
<para>
This allows <application>ecpg</> programs to contain SQL constructs
that use <literal>RETURNING</> internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
</para>
</listitem>
<listitem>
<para>
Improve selection of compiler flags for PL/Perl on Windows (Tom Lane)
</para>
<para>
This fix avoids possible crashes of PL/Perl due to inconsistent
assumptions about the width of <type>time_t</> values.
A side-effect that may be visible to extension developers is
that <literal>_USE_32BIT_TIME_T</> is no longer defined globally
in <productname>PostgreSQL</> Windows builds. This is not expected
to cause problems, because type <type>time_t</> is not used
in any <productname>PostgreSQL</> API definitions.
</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-9-3-18">
<title>Release 9.3.18</title>

156
doc/src/sgml/release-9.4.sgml
View File

@ -1,6 +1,162 @@
<!-- doc/src/sgml/release-9.4.sgml -->
<!-- See header comment in release.sgml about typical markup -->
<sect1 id="release-9-4-14">
<title>Release 9.4.14</title>
<formalpara>
<title>Release date:</title>
<para>2017-08-31</para>
</formalpara>
<para>
This release contains a small number of fixes from 9.4.13.
For information about new features in the 9.4 major release, see
<xref linkend="release-9-4">.
</para>
<sect2>
<title>Migration to Version 9.4.14</title>
<para>
A dump/restore is not required for those running 9.4.X.
</para>
<para>
However, if you are upgrading from a version earlier than 9.4.13,
see <xref linkend="release-9-4-13">.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem>
<!--
Author: Andres Freund <andres@anarazel.de>
Branch: REL9_4_STABLE [b51c8efc6] 2017-08-24 15:21:32 -0700
-->
<para>
Fix failure of walsender processes to respond to shutdown signals
(Marco Nenciarini)
</para>
<para>
A missed flag update resulted in walsenders continuing to run as long
as they had a standby server connected, preventing primary-server
shutdown unless immediate shutdown mode is used.
</para>
</listitem>
<listitem>
<para>
Show foreign tables
in <structname>information_schema</>.<structname>table_privileges</>
view (Peter Eisentraut)
</para>
<para>
All other relevant <structname>information_schema</> views include
foreign tables, but this one ignored them.
</para>
<para>
Since this view definition is installed by <application>initdb</>,
merely upgrading will not fix the problem. If you need to fix this
in an existing installation, you can, as a superuser, do this
in <application>psql</>:
<programlisting>
BEGIN;
DROP SCHEMA information_schema CASCADE;
\i <replaceable>SHAREDIR</>/information_schema.sql
COMMIT;
</programlisting>
(Run <literal>pg_config --sharedir</> if you're uncertain
where <replaceable>SHAREDIR</> is.) This must be repeated in each
database to be fixed.
</para>
</listitem>
<listitem>
<para>
Clean up handling of a fatal exit (e.g., due to receipt
of <systemitem>SIGTERM</>) that occurs while trying to execute
a <command>ROLLBACK</> of a failed transaction (Tom Lane)
</para>
<para>
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
message about <quote>cannot drop active portal</>.
</para>
</listitem>
<listitem>
<para>
Remove assertion that could trigger during a fatal exit (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Correctly identify columns that are of a range type or domain type over
a composite type or domain type being searched for (Tom Lane)
</para>
<para>
Certain <command>ALTER</> commands that change the definition of a
composite type or domain type are supposed to fail if there are any
stored values of that type in the database, because they lack the
infrastructure needed to update or check such values. Previously,
these checks could miss relevant values that are wrapped inside range
types or sub-domains, possibly allowing the database to become
inconsistent.
</para>
</listitem>
<listitem>
<para>
Fix crash in <application>pg_restore</> when using parallel mode and
using a list file to select a subset of items to restore (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Change <application>ecpg</>'s parser to allow <literal>RETURNING</>
clauses without attached C variables (Michael Meskes)
</para>
<para>
This allows <application>ecpg</> programs to contain SQL constructs
that use <literal>RETURNING</> internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
</para>
</listitem>
<listitem>
<para>
Improve selection of compiler flags for PL/Perl on Windows (Tom Lane)
</para>
<para>
This fix avoids possible crashes of PL/Perl due to inconsistent
assumptions about the width of <type>time_t</> values.
A side-effect that may be visible to extension developers is
that <literal>_USE_32BIT_TIME_T</> is no longer defined globally
in <productname>PostgreSQL</> Windows builds. This is not expected
to cause problems, because type <type>time_t</> is not used
in any <productname>PostgreSQL</> API definitions.
</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-9-4-13">
<title>Release 9.4.13</title>

146
doc/src/sgml/release-9.5.sgml
View File

@ -1,6 +1,152 @@
<!-- doc/src/sgml/release-9.5.sgml -->
<!-- See header comment in release.sgml about typical markup -->
<sect1 id="release-9-5-9">
<title>Release 9.5.9</title>
<formalpara>
<title>Release date:</title>
<para>2017-08-31</para>
</formalpara>
<para>
This release contains a small number of fixes from 9.5.8.
For information about new features in the 9.5 major release, see
<xref linkend="release-9-5">.
</para>
<sect2>
<title>Migration to Version 9.5.9</title>
<para>
A dump/restore is not required for those running 9.5.X.
</para>
<para>
However, if you are upgrading from a version earlier than 9.5.8,
see <xref linkend="release-9-5-8">.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem>
<para>
Show foreign tables
in <structname>information_schema</>.<structname>table_privileges</>
view (Peter Eisentraut)
</para>
<para>
All other relevant <structname>information_schema</> views include
foreign tables, but this one ignored them.
</para>
<para>
Since this view definition is installed by <application>initdb</>,
merely upgrading will not fix the problem. If you need to fix this
in an existing installation, you can, as a superuser, do this
in <application>psql</>:
<programlisting>
BEGIN;
DROP SCHEMA information_schema CASCADE;
\i <replaceable>SHAREDIR</>/information_schema.sql
COMMIT;
</programlisting>
(Run <literal>pg_config --sharedir</> if you're uncertain
where <replaceable>SHAREDIR</> is.) This must be repeated in each
database to be fixed.
</para>
</listitem>
<listitem>
<para>
Clean up handling of a fatal exit (e.g., due to receipt
of <systemitem>SIGTERM</>) that occurs while trying to execute
a <command>ROLLBACK</> of a failed transaction (Tom Lane)
</para>
<para>
This situation could result in an assertion failure. In production
builds, the exit would still occur, but it would log an unexpected
message about <quote>cannot drop active portal</>.
</para>
</listitem>
<listitem>
<para>
Remove assertion that could trigger during a fatal exit (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Correctly identify columns that are of a range type or domain type over
a composite type or domain type being searched for (Tom Lane)
</para>
<para>
Certain <command>ALTER</> commands that change the definition of a
composite type or domain type are supposed to fail if there are any
stored values of that type in the database, because they lack the
infrastructure needed to update or check such values. Previously,
these checks could miss relevant values that are wrapped inside range
types or sub-domains, possibly allowing the database to become
inconsistent.
</para>
</listitem>
<listitem>
<para>
Fix crash in <application>pg_restore</> when using parallel mode and
using a list file to select a subset of items to restore (Tom Lane)
</para>
</listitem>
<listitem>
<para>
Change <application>ecpg</>'s parser to allow <literal>RETURNING</>
clauses without attached C variables (Michael Meskes)
</para>
<para>
This allows <application>ecpg</> programs to contain SQL constructs
that use <literal>RETURNING</> internally (for example, inside a CTE)
rather than using it to define values to be returned to the client.
</para>
</listitem>
<listitem>
<para>
Improve selection of compiler flags for PL/Perl on Windows (Tom Lane)
</para>
<para>
This fix avoids possible crashes of PL/Perl due to inconsistent
assumptions about the width of <type>time_t</> values.
A side-effect that may be visible to extension developers is
that <literal>_USE_32BIT_TIME_T</> is no longer defined globally
in <productname>PostgreSQL</> Windows builds. This is not expected
to cause problems, because type <type>time_t</> is not used
in any <productname>PostgreSQL</> API definitions.
</para>
</listitem>
<listitem>
<para>
Fix <literal>make check</> to behave correctly when invoked via a
non-GNU make program (Thomas Munro)
</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-9-5-8">
<title>Release 9.5.8</title>

17
doc/src/sgml/release-9.6.sgml
View File

@ -35,23 +35,6 @@
<listitem>
<!--
Author: Andres Freund <andres@anarazel.de>
Branch: REL9_4_STABLE [b51c8efc6] 2017-08-24 15:21:32 -0700
-->
<para>
Fix failure of walsender processes to respond to shutdown signals
(Marco Nenciarini)
</para>
<para>
A missed flag update resulted in walsenders continuing to run as long
as they had a standby server connected, preventing primary-server
shutdown unless immediate shutdown mode is used.
</para>
</listitem>
<listitem>
<!--
Author: Peter Eisentraut <peter_e@gmx.net>
Branch: master [0659465ca] 2017-08-15 19:27:22 -0400
Branch: REL_10_STABLE [3ea58216d] 2017-08-15 19:30:35 -0400