mirror of
https://github.com/postgres/postgres.git
synced 2025-04-27 22:56:53 +03:00
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 1ff01b390 and c29c57890 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.)
This commit is contained in:
Tom Lane
parent
2a2e2e85e0
commit
168b41b65b
@ -1,6 +1,182 @@
|
|||||||
<!-- doc/src/sgml/release-9.2.sgml -->
|
<!-- doc/src/sgml/release-9.2.sgml -->
|
||||||
<!-- See header comment in release.sgml about typical markup -->
|
<!-- See header comment in release.sgml about typical markup -->
|
||||||
|
|
||||||
|
<sect1 id="release-9-2-24">
|
||||||
|
<title>Release 9.2.24</title>
|
||||||
|
|
||||||
|
<formalpara>
|
||||||
|
<title>Release date:</title>
|
||||||
|
<para>2017-11-09</para>
|
||||||
|
</formalpara>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This release contains a variety of fixes from 9.2.23.
|
||||||
|
For information about new features in the 9.2 major release, see
|
||||||
|
<xref linkend="release-9-2">.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This is expected to be the last <productname>PostgreSQL</productname>
|
||||||
|
release in the 9.2.X series. Users are encouraged to update to a newer
|
||||||
|
release branch soon.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<sect2>
|
||||||
|
<title>Migration to Version 9.2.24</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>
|
||||||
|
Properly reject attempts to convert infinite float values to
|
||||||
|
type <type>numeric</type> (Tom Lane, KaiGai Kohei)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Previously the behavior was platform-dependent.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix corner-case crashes when columns have been added to the end of a
|
||||||
|
view (Tom Lane)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Record proper dependencies when a view or rule
|
||||||
|
contains <structname>FieldSelect</structname>
|
||||||
|
or <structname>FieldStore</structname> expression nodes (Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Lack of these dependencies could allow a column or data
|
||||||
|
type <command>DROP</command> to go through when it ought to fail,
|
||||||
|
thereby causing later uses of the view or rule to get errors.
|
||||||
|
This patch does not do anything to protect existing views/rules,
|
||||||
|
only ones created in the future.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Correctly detect hashability of range data types (Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
The planner mistakenly assumed that any range type could be hashed
|
||||||
|
for use in hash joins or hash aggregation, but actually it must check
|
||||||
|
whether the range's subtype has hash support. This does not affect any
|
||||||
|
of the built-in range types, since they're all hashable anyway.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix low-probability loss of <command>NOTIFY</command> messages due to
|
||||||
|
XID wraparound (Marko Tiikkaja, Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
If a session executed no queries, but merely listened for
|
||||||
|
notifications, for more than 2 billion transactions, it started to miss
|
||||||
|
some notifications from concurrently-committing transactions.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Prevent low-probability crash in processing of nested trigger firings
|
||||||
|
(Tom Lane)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Correctly restore the umask setting when file creation fails
|
||||||
|
in <command>COPY</command> or <function>lo_export()</function>
|
||||||
|
(Peter Eisentraut)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Give a better error message for duplicate column names
|
||||||
|
in <command>ANALYZE</command> (Nathan Bossart)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix <application>libpq</application> to not require user's home
|
||||||
|
directory to exist (Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
In v10, failure to find the home directory while trying to
|
||||||
|
read <filename>~/.pgpass</filename> was treated as a hard error,
|
||||||
|
but it should just cause that file to not be found. Both v10 and
|
||||||
|
previous release branches made the same mistake when
|
||||||
|
reading <filename>~/.pg_service.conf</filename>, though this was less
|
||||||
|
obvious since that file is not sought unless a service name is
|
||||||
|
specified.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix <application>libpq</application> to guard against integer
|
||||||
|
overflow in the row count of a <structname>PGresult</structname>
|
||||||
|
(Michael Paquier)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Sync our copy of the timezone library with IANA release tzcode2017c
|
||||||
|
(Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This fixes various issues; the only one likely to be user-visible
|
||||||
|
is that the default DST rules for a POSIX-style zone name, if
|
||||||
|
no <filename>posixrules</filename> file exists in the timezone data
|
||||||
|
directory, now match current US law rather than what it was a dozen
|
||||||
|
years ago.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Update time zone data files to <application>tzdata</application>
|
||||||
|
release 2017c for DST law changes in Fiji, Namibia, Northern Cyprus,
|
||||||
|
Sudan, Tonga, and Turks & Caicos Islands, plus historical
|
||||||
|
corrections for Alaska, Apia, Burma, Calcutta, Detroit, Ireland,
|
||||||
|
Namibia, and Pago Pago.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
</itemizedlist>
|
||||||
|
|
||||||
|
</sect2>
|
||||||
|
</sect1>
|
||||||
|
|
||||||
<sect1 id="release-9-2-23">
|
<sect1 id="release-9-2-23">
|
||||||
<title>Release 9.2.23</title>
|
<title>Release 9.2.23</title>
|
||||||
|
|
||||||
|
|||||||
@ -1,6 +1,198 @@
|
|||||||
<!-- doc/src/sgml/release-9.3.sgml -->
|
<!-- doc/src/sgml/release-9.3.sgml -->
|
||||||
<!-- See header comment in release.sgml about typical markup -->
|
<!-- See header comment in release.sgml about typical markup -->
|
||||||
|
|
||||||
|
<sect1 id="release-9-3-20">
|
||||||
|
<title>Release 9.3.20</title>
|
||||||
|
|
||||||
|
<formalpara>
|
||||||
|
<title>Release date:</title>
|
||||||
|
<para>2017-11-09</para>
|
||||||
|
</formalpara>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This release contains a variety of fixes from 9.3.19.
|
||||||
|
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.20</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>
|
||||||
|
Properly reject attempts to convert infinite float values to
|
||||||
|
type <type>numeric</type> (Tom Lane, KaiGai Kohei)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Previously the behavior was platform-dependent.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix corner-case crashes when columns have been added to the end of a
|
||||||
|
view (Tom Lane)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Record proper dependencies when a view or rule
|
||||||
|
contains <structname>FieldSelect</structname>
|
||||||
|
or <structname>FieldStore</structname> expression nodes (Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Lack of these dependencies could allow a column or data
|
||||||
|
type <command>DROP</command> to go through when it ought to fail,
|
||||||
|
thereby causing later uses of the view or rule to get errors.
|
||||||
|
This patch does not do anything to protect existing views/rules,
|
||||||
|
only ones created in the future.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Correctly detect hashability of range data types (Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
The planner mistakenly assumed that any range type could be hashed
|
||||||
|
for use in hash joins or hash aggregation, but actually it must check
|
||||||
|
whether the range's subtype has hash support. This does not affect any
|
||||||
|
of the built-in range types, since they're all hashable anyway.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix low-probability loss of <command>NOTIFY</command> messages due to
|
||||||
|
XID wraparound (Marko Tiikkaja, Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
If a session executed no queries, but merely listened for
|
||||||
|
notifications, for more than 2 billion transactions, it started to miss
|
||||||
|
some notifications from concurrently-committing transactions.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Prevent low-probability crash in processing of nested trigger firings
|
||||||
|
(Tom Lane)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Correctly restore the umask setting when file creation fails
|
||||||
|
in <command>COPY</command> or <function>lo_export()</function>
|
||||||
|
(Peter Eisentraut)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Give a better error message for duplicate column names
|
||||||
|
in <command>ANALYZE</command> (Nathan Bossart)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix mis-parsing of the last line in a
|
||||||
|
non-newline-terminated <filename>pg_hba.conf</filename> file
|
||||||
|
(Tom Lane)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix <application>libpq</application> to not require user's home
|
||||||
|
directory to exist (Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
In v10, failure to find the home directory while trying to
|
||||||
|
read <filename>~/.pgpass</filename> was treated as a hard error,
|
||||||
|
but it should just cause that file to not be found. Both v10 and
|
||||||
|
previous release branches made the same mistake when
|
||||||
|
reading <filename>~/.pg_service.conf</filename>, though this was less
|
||||||
|
obvious since that file is not sought unless a service name is
|
||||||
|
specified.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix <application>libpq</application> to guard against integer
|
||||||
|
overflow in the row count of a <structname>PGresult</structname>
|
||||||
|
(Michael Paquier)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix <application>ecpg</application>'s handling of out-of-scope cursor
|
||||||
|
declarations with pointer or array variables (Michael Meskes)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Make ecpglib's Informix-compatibility mode ignore fractional digits in
|
||||||
|
integer input strings, as expected (Gao Zengqi, Michael Meskes)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Sync our copy of the timezone library with IANA release tzcode2017c
|
||||||
|
(Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This fixes various issues; the only one likely to be user-visible
|
||||||
|
is that the default DST rules for a POSIX-style zone name, if
|
||||||
|
no <filename>posixrules</filename> file exists in the timezone data
|
||||||
|
directory, now match current US law rather than what it was a dozen
|
||||||
|
years ago.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Update time zone data files to <application>tzdata</application>
|
||||||
|
release 2017c for DST law changes in Fiji, Namibia, Northern Cyprus,
|
||||||
|
Sudan, Tonga, and Turks & Caicos Islands, plus historical
|
||||||
|
corrections for Alaska, Apia, Burma, Calcutta, Detroit, Ireland,
|
||||||
|
Namibia, and Pago Pago.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
</itemizedlist>
|
||||||
|
|
||||||
|
</sect2>
|
||||||
|
</sect1>
|
||||||
|
|
||||||
<sect1 id="release-9-3-19">
|
<sect1 id="release-9-3-19">
|
||||||
<title>Release 9.3.19</title>
|
<title>Release 9.3.19</title>
|
||||||
|
|
||||||
|
|||||||
@ -1,6 +1,242 @@
|
|||||||
<!-- doc/src/sgml/release-9.4.sgml -->
|
<!-- doc/src/sgml/release-9.4.sgml -->
|
||||||
<!-- See header comment in release.sgml about typical markup -->
|
<!-- See header comment in release.sgml about typical markup -->
|
||||||
|
|
||||||
|
<sect1 id="release-9-4-15">
|
||||||
|
<title>Release 9.4.15</title>
|
||||||
|
|
||||||
|
<formalpara>
|
||||||
|
<title>Release date:</title>
|
||||||
|
<para>2017-11-09</para>
|
||||||
|
</formalpara>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This release contains a variety of fixes from 9.4.14.
|
||||||
|
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.15</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>
|
||||||
|
<para>
|
||||||
|
Fix crash when logical decoding is invoked from a SPI-using function,
|
||||||
|
in particular any function written in a PL language
|
||||||
|
(Tom Lane)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix <function>json_build_array()</function>,
|
||||||
|
<function>json_build_object()</function>, and their <type>jsonb</type>
|
||||||
|
equivalents to handle explicit <literal>VARIADIC</literal> arguments
|
||||||
|
correctly (Michael Paquier)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Properly reject attempts to convert infinite float values to
|
||||||
|
type <type>numeric</type> (Tom Lane, KaiGai Kohei)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Previously the behavior was platform-dependent.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix corner-case crashes when columns have been added to the end of a
|
||||||
|
view (Tom Lane)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Record proper dependencies when a view or rule
|
||||||
|
contains <structname>FieldSelect</structname>
|
||||||
|
or <structname>FieldStore</structname> expression nodes (Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Lack of these dependencies could allow a column or data
|
||||||
|
type <command>DROP</command> to go through when it ought to fail,
|
||||||
|
thereby causing later uses of the view or rule to get errors.
|
||||||
|
This patch does not do anything to protect existing views/rules,
|
||||||
|
only ones created in the future.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Correctly detect hashability of range data types (Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
The planner mistakenly assumed that any range type could be hashed
|
||||||
|
for use in hash joins or hash aggregation, but actually it must check
|
||||||
|
whether the range's subtype has hash support. This does not affect any
|
||||||
|
of the built-in range types, since they're all hashable anyway.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix low-probability loss of <command>NOTIFY</command> messages due to
|
||||||
|
XID wraparound (Marko Tiikkaja, Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
If a session executed no queries, but merely listened for
|
||||||
|
notifications, for more than 2 billion transactions, it started to miss
|
||||||
|
some notifications from concurrently-committing transactions.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Avoid <systemitem>SIGBUS</systemitem> crash on Linux when a DSM memory
|
||||||
|
request exceeds the space available in <systemitem>tmpfs</systemitem>
|
||||||
|
(Thomas Munro)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Prevent low-probability crash in processing of nested trigger firings
|
||||||
|
(Tom Lane)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Allow <command>COPY</command>'s <literal>FREEZE</literal> option to
|
||||||
|
work when the transaction isolation level is <literal>REPEATABLE
|
||||||
|
READ</literal> or higher (Noah Misch)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This case was unintentionally broken by a previous bug fix.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Correctly restore the umask setting when file creation fails
|
||||||
|
in <command>COPY</command> or <function>lo_export()</function>
|
||||||
|
(Peter Eisentraut)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Give a better error message for duplicate column names
|
||||||
|
in <command>ANALYZE</command> (Nathan Bossart)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix mis-parsing of the last line in a
|
||||||
|
non-newline-terminated <filename>pg_hba.conf</filename> file
|
||||||
|
(Tom Lane)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix <application>libpq</application> to not require user's home
|
||||||
|
directory to exist (Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
In v10, failure to find the home directory while trying to
|
||||||
|
read <filename>~/.pgpass</filename> was treated as a hard error,
|
||||||
|
but it should just cause that file to not be found. Both v10 and
|
||||||
|
previous release branches made the same mistake when
|
||||||
|
reading <filename>~/.pg_service.conf</filename>, though this was less
|
||||||
|
obvious since that file is not sought unless a service name is
|
||||||
|
specified.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix <application>libpq</application> to guard against integer
|
||||||
|
overflow in the row count of a <structname>PGresult</structname>
|
||||||
|
(Michael Paquier)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix <application>ecpg</application>'s handling of out-of-scope cursor
|
||||||
|
declarations with pointer or array variables (Michael Meskes)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
In ecpglib, correctly handle backslashes in string literals depending
|
||||||
|
on whether <varname>standard_conforming_strings</varname> is set
|
||||||
|
(Tsunakawa Takayuki)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Make ecpglib's Informix-compatibility mode ignore fractional digits in
|
||||||
|
integer input strings, as expected (Gao Zengqi, Michael Meskes)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Sync our copy of the timezone library with IANA release tzcode2017c
|
||||||
|
(Tom Lane)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This fixes various issues; the only one likely to be user-visible
|
||||||
|
is that the default DST rules for a POSIX-style zone name, if
|
||||||
|
no <filename>posixrules</filename> file exists in the timezone data
|
||||||
|
directory, now match current US law rather than what it was a dozen
|
||||||
|
years ago.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Update time zone data files to <application>tzdata</application>
|
||||||
|
release 2017c for DST law changes in Fiji, Namibia, Northern Cyprus,
|
||||||
|
Sudan, Tonga, and Turks & Caicos Islands, plus historical
|
||||||
|
corrections for Alaska, Apia, Burma, Calcutta, Detroit, Ireland,
|
||||||
|
Namibia, and Pago Pago.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
</itemizedlist>
|
||||||
|
|
||||||
|
</sect2>
|
||||||
|
</sect1>
|
||||||
|
|
||||||
<sect1 id="release-9-4-14">
|
<sect1 id="release-9-4-14">
|
||||||
<title>Release 9.4.14</title>
|
<title>Release 9.4.14</title>
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user