<!-- doc/src/sgml/release-9.1.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-1-20">
+ <title>Release 9.1.20</title>
+
+ <note>
+ <title>Release Date</title>
+ <simpara>2016-02-11</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 9.1.19.
+ For information about new features in the 9.1 major release, see
+ <xref linkend="release-9-1">.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.1.20</title>
+
+ <para>
+ A dump/restore is not required for those running 9.1.X.
+ </para>
+
+ <para>
+ However, if you are upgrading from a version earlier than 9.1.16,
+ see <xref linkend="release-9-1-16">.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Perform an immediate shutdown if the <filename>postmaster.pid</> file
+ is removed (Tom Lane)
+ </para>
+
+ <para>
+ The postmaster now checks every minute or so
+ that <filename>postmaster.pid</> is still there and still contains its
+ own PID. If not, it performs an immediate shutdown, as though it had
+ received <systemitem>SIGQUIT</>. The main motivation for this change
+ is to ensure that failed buildfarm runs will get cleaned up without
+ manual intervention; but it also serves to limit the bad effects if a
+ DBA forcibly removes <filename>postmaster.pid</> and then starts a new
+ postmaster.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <literal>SERIALIZABLE</> transaction isolation mode, serialization
+ anomalies could be missed due to race conditions during insertions
+ (Kevin Grittner, Thomas Munro)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix failure to emit appropriate WAL records when doing <literal>ALTER
+ TABLE ... SET TABLESPACE</> for unlogged relations (Michael Paquier,
+ Andres Freund)
+ </para>
+
+ <para>
+ Even though the relation's data is unlogged, the move must be logged or
+ the relation will be inaccessible after a standby is promoted to master.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible misinitialization of unlogged relations at the end of
+ crash recovery (Andres Freund, Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>ALTER COLUMN TYPE</> to reconstruct inherited check
+ constraints properly (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>REASSIGN OWNED</> to change ownership of composite types
+ properly (Álvaro Herrera)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>REASSIGN OWNED</> and <command>ALTER OWNER</> to correctly
+ update granted-permissions lists when changing owners of data types,
+ foreign data wrappers, or foreign servers (Bruce Momjian,
+ Álvaro Herrera)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>REASSIGN OWNED</> to ignore foreign user mappings,
+ rather than fail (Álvaro Herrera)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add more defenses against bad planner cost estimates for GIN index
+ scans when the index's internal statistics are very out-of-date
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make planner cope with hypothetical GIN indexes suggested by an index
+ advisor plug-in (Julien Rouhaud)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix dumping of whole-row Vars in <literal>ROW()</>
+ and <literal>VALUES()</> lists (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible internal overflow in <type>numeric</> division
+ (Dean Rasheed)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix enforcement of restrictions inside parentheses within regular
+ expression lookahead constraints (Tom Lane)
+ </para>
+
+ <para>
+ Lookahead constraints aren't allowed to contain backrefs, and
+ parentheses within them are always considered non-capturing, according
+ to the manual. However, the code failed to handle these cases properly
+ inside a parenthesized subexpression, and would give unexpected
+ results.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Conversion of regular expressions to indexscan bounds could produce
+ incorrect bounds from regexps containing lookahead constraints
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix regular-expression compiler to handle loops of constraint arcs
+ (Tom Lane)
+ </para>
+
+ <para>
+ The code added for CVE-2007-4772 was both incomplete, in that it didn't
+ handle loops involving more than one state, and incorrect, in that it
+ could cause assertion failures (though there seem to be no bad
+ consequences of that in a non-assert build). Multi-state loops would
+ cause the compiler to run until the query was canceled or it reached
+ the too-many-states error condition.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve memory-usage accounting in regular-expression compiler
+ (Tom Lane)
+ </para>
+
+ <para>
+ This causes the code to emit <quote>regular expression is too
+ complex</> errors in some cases that previously used unreasonable
+ amounts of time and memory.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve performance of regular-expression compiler (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <literal>%h</> and <literal>%r</> escapes
+ in <varname>log_line_prefix</> work for messages emitted due
+ to <varname>log_connections</> (Tom Lane)
+ </para>
+
+ <para>
+ Previously, <literal>%h</>/<literal>%r</> started to work just after a
+ new session had emitted the <quote>connection received</> log message;
+ now they work for that message too.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, ensure the shared-memory mapping handle gets closed in
+ child processes that don't need it (Tom Lane, Amit Kapila)
+ </para>
+
+ <para>
+ This oversight resulted in failure to recover from crashes
+ whenever <varname>logging_collector</> is turned on.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible failure to detect socket EOF in non-blocking mode on
+ Windows (Tom Lane)
+ </para>
+
+ <para>
+ It's not entirely clear whether this problem can happen in pre-9.5
+ branches, but if it did, the symptom would be that a walsender process
+ would wait indefinitely rather than noticing a loss of connection.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid leaking a token handle during SSPI authentication
+ (Christian Ullrich)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <application>psql</>, ensure that <application>libreadline</>'s idea
+ of the screen size is updated when the terminal window size changes
+ (Merlin Moncure)
+ </para>
+
+ <para>
+ Previously, <application>libreadline</> did not notice if the window
+ was resized during query output, leading to strange behavior during
+ later input of multiline queries.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>psql</>'s <literal>\det</> command to interpret its
+ pattern argument the same way as other <literal>\d</> commands with
+ potentially schema-qualified patterns do (Reece Hart)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid possible crash in <application>psql</>'s <literal>\c</> command
+ when previous connection was via Unix socket and command specifies a
+ new hostname and same username (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <literal>pg_ctl start -w</>, test child process status directly
+ rather than relying on heuristics (Tom Lane, Michael Paquier)
+ </para>
+
+ <para>
+ Previously, <application>pg_ctl</> relied on an assumption that the new
+ postmaster would always create <filename>postmaster.pid</> within five
+ seconds. But that can fail on heavily-loaded systems,
+ causing <application>pg_ctl</> to report incorrectly that the
+ postmaster failed to start.
+ </para>
+
+ <para>
+ Except on Windows, this change also means that a <literal>pg_ctl start
+ -w</> done immediately after another such command will now reliably
+ fail, whereas previously it would report success if done within two
+ seconds of the first command.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <literal>pg_ctl start -w</>, don't attempt to use a wildcard listen
+ address to connect to the postmaster (Kondo Yuta)
+ </para>
+
+ <para>
+ On Windows, <application>pg_ctl</> would fail to detect postmaster
+ startup if <varname>listen_addresses</> is set to <literal>0.0.0.0</>
+ or <literal>::</>, because it would try to use that value verbatim as
+ the address to connect to, which doesn't work. Instead assume
+ that <literal>127.0.0.1</> or <literal>::1</>, respectively, is the
+ right thing to use.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <application>pg_ctl</> on Windows, check service status to decide
+ where to send output, rather than checking if standard output is a
+ terminal (Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <application>pg_dump</> and <application>pg_basebackup</>, adopt
+ the GNU convention for handling tar-archive members exceeding 8GB
+ (Tom Lane)
+ </para>
+
+ <para>
+ The POSIX standard for <literal>tar</> file format does not allow
+ archive member files to exceed 8GB, but most modern implementations
+ of <application>tar</> support an extension that fixes that. Adopt
+ this extension so that <application>pg_dump</> with <option>-Ft</> no
+ longer fails on tables with more than 8GB of data, and so
+ that <application>pg_basebackup</> can handle files larger than 8GB.
+ In addition, fix some portability issues that could cause failures for
+ members between 4GB and 8GB on some platforms. Potentially these
+ problems could cause unrecoverable data loss due to unreadable backup
+ files.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix assorted corner-case bugs in <application>pg_dump</>'s processing
+ of extension member objects (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <application>pg_dump</> mark a view's triggers as needing to be
+ processed after its rule, to prevent possible failure during
+ parallel <application>pg_restore</> (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure that relation option values are properly quoted
+ in <application>pg_dump</> (Kouhei Sutou, Tom Lane)
+ </para>
+
+ <para>
+ A reloption value that isn't a simple identifier or number could lead
+ to dump/reload failures due to syntax errors in CREATE statements
+ issued by <application>pg_dump</>. This is not an issue with any
+ reloption currently supported by core <productname>PostgreSQL</>, but
+ extensions could allow reloptions that cause the problem.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>pg_upgrade</>'s file-copying code to handle errors
+ properly on Windows (Bruce Momjian)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Install guards in <application>pgbench</> against corner-case overflow
+ conditions during evaluation of script-specified division or modulo
+ operators (Fabien Coelho, Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent certain <application>PL/Java</> parameters from being set by
+ non-superusers (Noah Misch)
+ </para>
+
+ <para>
+ This change mitigates a <application>PL/Java</> security bug
+ (CVE-2016-0766), which was fixed in <application>PL/Java</> by marking
+ these parameters as superuser-only. To fix the security hazard for
+ sites that update <productname>PostgreSQL</> more frequently
+ than <application>PL/Java</>, make the core code aware of them also.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve <application>libpq</>'s handling of out-of-memory situations
+ (Michael Paquier, Amit Kapila, Heikki Linnakangas)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix order of arguments
+ in <application>ecpg</>-generated <literal>typedef</> statements
+ (Michael Meskes)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use <literal>%g</> not <literal>%f</> format
+ in <application>ecpg</>'s <function>PGTYPESnumeric_from_double()</>
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>ecpg</>-supplied header files to not contain comments
+ continued from a preprocessor directive line onto the next line
+ (Michael Meskes)
+ </para>
+
+ <para>
+ Such a comment is rejected by <application>ecpg</>. It's not yet clear
+ whether <application>ecpg</> itself should be changed.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure that <filename>contrib/pgcrypto</>'s <function>crypt()</>
+ function can be interrupted by query cancel (Andreas Karlsson)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Accept <application>flex</> versions later than 2.5.x
+ (Tom Lane, Michael Paquier)
+ </para>
+
+ <para>
+ Now that flex 2.6.0 has been released, the version checks in our build
+ scripts needed to be adjusted.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Install our <filename>missing</> script where PGXS builds can find it
+ (Jim Nasby)
+ </para>
+
+ <para>
+ This allows sane behavior in a PGXS build done on a machine where build
+ tools such as <application>bison</> are missing.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure that <filename>dynloader.h</> is included in the installed
+ header files in MSVC builds (Bruce Momjian, Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add variant regression test expected-output file to match behavior of
+ current <application>libxml2</> (Tom Lane)
+ </para>
+
+ <para>
+ The fix for <application>libxml2</>'s CVE-2015-7499 causes it not to
+ output error context reports in some cases where it used to do so.
+ This seems to be a bug, but we'll probably have to live with it for
+ some time, so work around it.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</> release 2016a for
+ DST law changes in Cayman Islands, Metlakatla, and Trans-Baikal
+ Territory (Zabaykalsky Krai), plus historical corrections for Pakistan.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-1-19">
<title>Release 9.1.19</title>
<!-- doc/src/sgml/release-9.2.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-2-15">
+ <title>Release 9.2.15</title>
+
+ <note>
+ <title>Release Date</title>
+ <simpara>2016-02-11</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 9.2.14.
+ For information about new features in the 9.2 major release, see
+ <xref linkend="release-9-2">.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.2.15</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.11,
+ see <xref linkend="release-9-2-11">.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Perform an immediate shutdown if the <filename>postmaster.pid</> file
+ is removed (Tom Lane)
+ </para>
+
+ <para>
+ The postmaster now checks every minute or so
+ that <filename>postmaster.pid</> is still there and still contains its
+ own PID. If not, it performs an immediate shutdown, as though it had
+ received <systemitem>SIGQUIT</>. The main motivation for this change
+ is to ensure that failed buildfarm runs will get cleaned up without
+ manual intervention; but it also serves to limit the bad effects if a
+ DBA forcibly removes <filename>postmaster.pid</> and then starts a new
+ postmaster.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <literal>SERIALIZABLE</> transaction isolation mode, serialization
+ anomalies could be missed due to race conditions during insertions
+ (Kevin Grittner, Thomas Munro)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix failure to emit appropriate WAL records when doing <literal>ALTER
+ TABLE ... SET TABLESPACE</> for unlogged relations (Michael Paquier,
+ Andres Freund)
+ </para>
+
+ <para>
+ Even though the relation's data is unlogged, the move must be logged or
+ the relation will be inaccessible after a standby is promoted to master.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible misinitialization of unlogged relations at the end of
+ crash recovery (Andres Freund, Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>ALTER COLUMN TYPE</> to reconstruct inherited check
+ constraints properly (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>REASSIGN OWNED</> to change ownership of composite types
+ properly (Álvaro Herrera)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>REASSIGN OWNED</> and <command>ALTER OWNER</> to correctly
+ update granted-permissions lists when changing owners of data types,
+ foreign data wrappers, or foreign servers (Bruce Momjian,
+ Álvaro Herrera)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>REASSIGN OWNED</> to ignore foreign user mappings,
+ rather than fail (Álvaro Herrera)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add more defenses against bad planner cost estimates for GIN index
+ scans when the index's internal statistics are very out-of-date
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make planner cope with hypothetical GIN indexes suggested by an index
+ advisor plug-in (Julien Rouhaud)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix dumping of whole-row Vars in <literal>ROW()</>
+ and <literal>VALUES()</> lists (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible internal overflow in <type>numeric</> division
+ (Dean Rasheed)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix enforcement of restrictions inside parentheses within regular
+ expression lookahead constraints (Tom Lane)
+ </para>
+
+ <para>
+ Lookahead constraints aren't allowed to contain backrefs, and
+ parentheses within them are always considered non-capturing, according
+ to the manual. However, the code failed to handle these cases properly
+ inside a parenthesized subexpression, and would give unexpected
+ results.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Conversion of regular expressions to indexscan bounds could produce
+ incorrect bounds from regexps containing lookahead constraints
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix regular-expression compiler to handle loops of constraint arcs
+ (Tom Lane)
+ </para>
+
+ <para>
+ The code added for CVE-2007-4772 was both incomplete, in that it didn't
+ handle loops involving more than one state, and incorrect, in that it
+ could cause assertion failures (though there seem to be no bad
+ consequences of that in a non-assert build). Multi-state loops would
+ cause the compiler to run until the query was canceled or it reached
+ the too-many-states error condition.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve memory-usage accounting in regular-expression compiler
+ (Tom Lane)
+ </para>
+
+ <para>
+ This causes the code to emit <quote>regular expression is too
+ complex</> errors in some cases that previously used unreasonable
+ amounts of time and memory.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve performance of regular-expression compiler (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <literal>%h</> and <literal>%r</> escapes
+ in <varname>log_line_prefix</> work for messages emitted due
+ to <varname>log_connections</> (Tom Lane)
+ </para>
+
+ <para>
+ Previously, <literal>%h</>/<literal>%r</> started to work just after a
+ new session had emitted the <quote>connection received</> log message;
+ now they work for that message too.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, ensure the shared-memory mapping handle gets closed in
+ child processes that don't need it (Tom Lane, Amit Kapila)
+ </para>
+
+ <para>
+ This oversight resulted in failure to recover from crashes
+ whenever <varname>logging_collector</> is turned on.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible failure to detect socket EOF in non-blocking mode on
+ Windows (Tom Lane)
+ </para>
+
+ <para>
+ It's not entirely clear whether this problem can happen in pre-9.5
+ branches, but if it did, the symptom would be that a walsender process
+ would wait indefinitely rather than noticing a loss of connection.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid leaking a token handle during SSPI authentication
+ (Christian Ullrich)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <application>psql</>, ensure that <application>libreadline</>'s idea
+ of the screen size is updated when the terminal window size changes
+ (Merlin Moncure)
+ </para>
+
+ <para>
+ Previously, <application>libreadline</> did not notice if the window
+ was resized during query output, leading to strange behavior during
+ later input of multiline queries.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>psql</>'s <literal>\det</> command to interpret its
+ pattern argument the same way as other <literal>\d</> commands with
+ potentially schema-qualified patterns do (Reece Hart)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid possible crash in <application>psql</>'s <literal>\c</> command
+ when previous connection was via Unix socket and command specifies a
+ new hostname and same username (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <literal>pg_ctl start -w</>, test child process status directly
+ rather than relying on heuristics (Tom Lane, Michael Paquier)
+ </para>
+
+ <para>
+ Previously, <application>pg_ctl</> relied on an assumption that the new
+ postmaster would always create <filename>postmaster.pid</> within five
+ seconds. But that can fail on heavily-loaded systems,
+ causing <application>pg_ctl</> to report incorrectly that the
+ postmaster failed to start.
+ </para>
+
+ <para>
+ Except on Windows, this change also means that a <literal>pg_ctl start
+ -w</> done immediately after another such command will now reliably
+ fail, whereas previously it would report success if done within two
+ seconds of the first command.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <literal>pg_ctl start -w</>, don't attempt to use a wildcard listen
+ address to connect to the postmaster (Kondo Yuta)
+ </para>
+
+ <para>
+ On Windows, <application>pg_ctl</> would fail to detect postmaster
+ startup if <varname>listen_addresses</> is set to <literal>0.0.0.0</>
+ or <literal>::</>, because it would try to use that value verbatim as
+ the address to connect to, which doesn't work. Instead assume
+ that <literal>127.0.0.1</> or <literal>::1</>, respectively, is the
+ right thing to use.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <application>pg_ctl</> on Windows, check service status to decide
+ where to send output, rather than checking if standard output is a
+ terminal (Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <application>pg_dump</> and <application>pg_basebackup</>, adopt
+ the GNU convention for handling tar-archive members exceeding 8GB
+ (Tom Lane)
+ </para>
+
+ <para>
+ The POSIX standard for <literal>tar</> file format does not allow
+ archive member files to exceed 8GB, but most modern implementations
+ of <application>tar</> support an extension that fixes that. Adopt
+ this extension so that <application>pg_dump</> with <option>-Ft</> no
+ longer fails on tables with more than 8GB of data, and so
+ that <application>pg_basebackup</> can handle files larger than 8GB.
+ In addition, fix some portability issues that could cause failures for
+ members between 4GB and 8GB on some platforms. Potentially these
+ problems could cause unrecoverable data loss due to unreadable backup
+ files.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix assorted corner-case bugs in <application>pg_dump</>'s processing
+ of extension member objects (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <application>pg_dump</> mark a view's triggers as needing to be
+ processed after its rule, to prevent possible failure during
+ parallel <application>pg_restore</> (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure that relation option values are properly quoted
+ in <application>pg_dump</> (Kouhei Sutou, Tom Lane)
+ </para>
+
+ <para>
+ A reloption value that isn't a simple identifier or number could lead
+ to dump/reload failures due to syntax errors in CREATE statements
+ issued by <application>pg_dump</>. This is not an issue with any
+ reloption currently supported by core <productname>PostgreSQL</>, but
+ extensions could allow reloptions that cause the problem.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>pg_upgrade</>'s file-copying code to handle errors
+ properly on Windows (Bruce Momjian)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Install guards in <application>pgbench</> against corner-case overflow
+ conditions during evaluation of script-specified division or modulo
+ operators (Fabien Coelho, Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix failure to localize messages emitted
+ by <application>pg_receivexlog</> and <application>pg_recvlogical</>
+ (Ioseph Kim)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid dump/reload problems when using both <application>plpython2</>
+ and <application>plpython3</> (Tom Lane)
+ </para>
+
+ <para>
+ In principle, both versions of <application>PL/Python</> can be used in
+ the same database, though not in the same session (because the two
+ versions of <application>libpython</> cannot safely be used concurrently).
+ However, <application>pg_restore</> and <application>pg_upgrade</> both
+ do things that can fall foul of the same-session restriction. Work
+ around that by changing the timing of the check.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>PL/Python</> regression tests to pass with Python 3.5
+ (Peter Eisentraut)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent certain <application>PL/Java</> parameters from being set by
+ non-superusers (Noah Misch)
+ </para>
+
+ <para>
+ This change mitigates a <application>PL/Java</> security bug
+ (CVE-2016-0766), which was fixed in <application>PL/Java</> by marking
+ these parameters as superuser-only. To fix the security hazard for
+ sites that update <productname>PostgreSQL</> more frequently
+ than <application>PL/Java</>, make the core code aware of them also.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve <application>libpq</>'s handling of out-of-memory situations
+ (Michael Paquier, Amit Kapila, Heikki Linnakangas)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix order of arguments
+ in <application>ecpg</>-generated <literal>typedef</> statements
+ (Michael Meskes)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use <literal>%g</> not <literal>%f</> format
+ in <application>ecpg</>'s <function>PGTYPESnumeric_from_double()</>
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>ecpg</>-supplied header files to not contain comments
+ continued from a preprocessor directive line onto the next line
+ (Michael Meskes)
+ </para>
+
+ <para>
+ Such a comment is rejected by <application>ecpg</>. It's not yet clear
+ whether <application>ecpg</> itself should be changed.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure that <filename>contrib/pgcrypto</>'s <function>crypt()</>
+ function can be interrupted by query cancel (Andreas Karlsson)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Accept <application>flex</> versions later than 2.5.x
+ (Tom Lane, Michael Paquier)
+ </para>
+
+ <para>
+ Now that flex 2.6.0 has been released, the version checks in our build
+ scripts needed to be adjusted.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Install our <filename>missing</> script where PGXS builds can find it
+ (Jim Nasby)
+ </para>
+
+ <para>
+ This allows sane behavior in a PGXS build done on a machine where build
+ tools such as <application>bison</> are missing.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure that <filename>dynloader.h</> is included in the installed
+ header files in MSVC builds (Bruce Momjian, Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add variant regression test expected-output file to match behavior of
+ current <application>libxml2</> (Tom Lane)
+ </para>
+
+ <para>
+ The fix for <application>libxml2</>'s CVE-2015-7499 causes it not to
+ output error context reports in some cases where it used to do so.
+ This seems to be a bug, but we'll probably have to live with it for
+ some time, so work around it.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</> release 2016a for
+ DST law changes in Cayman Islands, Metlakatla, and Trans-Baikal
+ Territory (Zabaykalsky Krai), plus historical corrections for Pakistan.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-2-14">
<title>Release 9.2.14</title>
<!-- doc/src/sgml/release-9.3.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-3-11">
+ <title>Release 9.3.11</title>
+
+ <note>
+ <title>Release Date</title>
+ <simpara>2016-02-11</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 9.3.10.
+ 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.11</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.9,
+ see <xref linkend="release-9-3-9">.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Perform an immediate shutdown if the <filename>postmaster.pid</> file
+ is removed (Tom Lane)
+ </para>
+
+ <para>
+ The postmaster now checks every minute or so
+ that <filename>postmaster.pid</> is still there and still contains its
+ own PID. If not, it performs an immediate shutdown, as though it had
+ received <systemitem>SIGQUIT</>. The main motivation for this change
+ is to ensure that failed buildfarm runs will get cleaned up without
+ manual intervention; but it also serves to limit the bad effects if a
+ DBA forcibly removes <filename>postmaster.pid</> and then starts a new
+ postmaster.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <literal>SERIALIZABLE</> transaction isolation mode, serialization
+ anomalies could be missed due to race conditions during insertions
+ (Kevin Grittner, Thomas Munro)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix failure to emit appropriate WAL records when doing <literal>ALTER
+ TABLE ... SET TABLESPACE</> for unlogged relations (Michael Paquier,
+ Andres Freund)
+ </para>
+
+ <para>
+ Even though the relation's data is unlogged, the move must be logged or
+ the relation will be inaccessible after a standby is promoted to master.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible misinitialization of unlogged relations at the end of
+ crash recovery (Andres Freund, Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure walsender slots are fully re-initialized when being re-used
+ (Magnus Hagander)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>ALTER COLUMN TYPE</> to reconstruct inherited check
+ constraints properly (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>REASSIGN OWNED</> to change ownership of composite types
+ properly (Álvaro Herrera)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>REASSIGN OWNED</> and <command>ALTER OWNER</> to correctly
+ update granted-permissions lists when changing owners of data types,
+ foreign data wrappers, or foreign servers (Bruce Momjian,
+ Álvaro Herrera)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <command>REASSIGN OWNED</> to ignore foreign user mappings,
+ rather than fail (Álvaro Herrera)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible crash after doing query rewrite for an updatable view
+ (Stephen Frost)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner's handling of <literal>LATERAL</> references (Tom
+ Lane)
+ </para>
+
+ <para>
+ This fixes some corner cases that led to <quote>failed to build any
+ N-way joins</> or <quote>could not devise a query plan</> planner
+ failures.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add more defenses against bad planner cost estimates for GIN index
+ scans when the index's internal statistics are very out-of-date
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make planner cope with hypothetical GIN indexes suggested by an index
+ advisor plug-in (Julien Rouhaud)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Speed up generation of unique table aliases in <command>EXPLAIN</> and
+ rule dumping, and ensure that generated aliases do not
+ exceed <literal>NAMEDATALEN</> (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix dumping of whole-row Vars in <literal>ROW()</>
+ and <literal>VALUES()</> lists (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible internal overflow in <type>numeric</> division
+ (Dean Rasheed)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix enforcement of restrictions inside parentheses within regular
+ expression lookahead constraints (Tom Lane)
+ </para>
+
+ <para>
+ Lookahead constraints aren't allowed to contain backrefs, and
+ parentheses within them are always considered non-capturing, according
+ to the manual. However, the code failed to handle these cases properly
+ inside a parenthesized subexpression, and would give unexpected
+ results.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Conversion of regular expressions to indexscan bounds could produce
+ incorrect bounds from regexps containing lookahead constraints
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix regular-expression compiler to handle loops of constraint arcs
+ (Tom Lane)
+ </para>
+
+ <para>
+ The code added for CVE-2007-4772 was both incomplete, in that it didn't
+ handle loops involving more than one state, and incorrect, in that it
+ could cause assertion failures (though there seem to be no bad
+ consequences of that in a non-assert build). Multi-state loops would
+ cause the compiler to run until the query was canceled or it reached
+ the too-many-states error condition.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve memory-usage accounting in regular-expression compiler
+ (Tom Lane)
+ </para>
+
+ <para>
+ This causes the code to emit <quote>regular expression is too
+ complex</> errors in some cases that previously used unreasonable
+ amounts of time and memory.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve performance of regular-expression compiler (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <literal>%h</> and <literal>%r</> escapes
+ in <varname>log_line_prefix</> work for messages emitted due
+ to <varname>log_connections</> (Tom Lane)
+ </para>
+
+ <para>
+ Previously, <literal>%h</>/<literal>%r</> started to work just after a
+ new session had emitted the <quote>connection received</> log message;
+ now they work for that message too.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ On Windows, ensure the shared-memory mapping handle gets closed in
+ child processes that don't need it (Tom Lane, Amit Kapila)
+ </para>
+
+ <para>
+ This oversight resulted in failure to recover from crashes
+ whenever <varname>logging_collector</> is turned on.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix possible failure to detect socket EOF in non-blocking mode on
+ Windows (Tom Lane)
+ </para>
+
+ <para>
+ It's not entirely clear whether this problem can happen in pre-9.5
+ branches, but if it did, the symptom would be that a walsender process
+ would wait indefinitely rather than noticing a loss of connection.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid leaking a token handle during SSPI authentication
+ (Christian Ullrich)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <application>psql</>, ensure that <application>libreadline</>'s idea
+ of the screen size is updated when the terminal window size changes
+ (Merlin Moncure)
+ </para>
+
+ <para>
+ Previously, <application>libreadline</> did not notice if the window
+ was resized during query output, leading to strange behavior during
+ later input of multiline queries.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>psql</>'s <literal>\det</> command to interpret its
+ pattern argument the same way as other <literal>\d</> commands with
+ potentially schema-qualified patterns do (Reece Hart)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid possible crash in <application>psql</>'s <literal>\c</> command
+ when previous connection was via Unix socket and command specifies a
+ new hostname and same username (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <literal>pg_ctl start -w</>, test child process status directly
+ rather than relying on heuristics (Tom Lane, Michael Paquier)
+ </para>
+
+ <para>
+ Previously, <application>pg_ctl</> relied on an assumption that the new
+ postmaster would always create <filename>postmaster.pid</> within five
+ seconds. But that can fail on heavily-loaded systems,
+ causing <application>pg_ctl</> to report incorrectly that the
+ postmaster failed to start.
+ </para>
+
+ <para>
+ Except on Windows, this change also means that a <literal>pg_ctl start
+ -w</> done immediately after another such command will now reliably
+ fail, whereas previously it would report success if done within two
+ seconds of the first command.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <literal>pg_ctl start -w</>, don't attempt to use a wildcard listen
+ address to connect to the postmaster (Kondo Yuta)
+ </para>
+
+ <para>
+ On Windows, <application>pg_ctl</> would fail to detect postmaster
+ startup if <varname>listen_addresses</> is set to <literal>0.0.0.0</>
+ or <literal>::</>, because it would try to use that value verbatim as
+ the address to connect to, which doesn't work. Instead assume
+ that <literal>127.0.0.1</> or <literal>::1</>, respectively, is the
+ right thing to use.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <application>pg_ctl</> on Windows, check service status to decide
+ where to send output, rather than checking if standard output is a
+ terminal (Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ In <application>pg_dump</> and <application>pg_basebackup</>, adopt
+ the GNU convention for handling tar-archive members exceeding 8GB
+ (Tom Lane)
+ </para>
+
+ <para>
+ The POSIX standard for <literal>tar</> file format does not allow
+ archive member files to exceed 8GB, but most modern implementations
+ of <application>tar</> support an extension that fixes that. Adopt
+ this extension so that <application>pg_dump</> with <option>-Ft</> no
+ longer fails on tables with more than 8GB of data, and so
+ that <application>pg_basebackup</> can handle files larger than 8GB.
+ In addition, fix some portability issues that could cause failures for
+ members between 4GB and 8GB on some platforms. Potentially these
+ problems could cause unrecoverable data loss due to unreadable backup
+ files.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix assorted corner-case bugs in <application>pg_dump</>'s processing
+ of extension member objects (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Make <application>pg_dump</> mark a view's triggers as needing to be
+ processed after its rule, to prevent possible failure during
+ parallel <application>pg_restore</> (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure that relation option values are properly quoted
+ in <application>pg_dump</> (Kouhei Sutou, Tom Lane)
+ </para>
+
+ <para>
+ A reloption value that isn't a simple identifier or number could lead
+ to dump/reload failures due to syntax errors in CREATE statements
+ issued by <application>pg_dump</>. This is not an issue with any
+ reloption currently supported by core <productname>PostgreSQL</>, but
+ extensions could allow reloptions that cause the problem.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid repeated password prompts during parallel <application>pg_dump</>
+ (Zeus Kronion)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>pg_upgrade</>'s file-copying code to handle errors
+ properly on Windows (Bruce Momjian)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Install guards in <application>pgbench</> against corner-case overflow
+ conditions during evaluation of script-specified division or modulo
+ operators (Fabien Coelho, Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix failure to localize messages emitted
+ by <application>pg_receivexlog</> and <application>pg_recvlogical</>
+ (Ioseph Kim)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Avoid dump/reload problems when using both <application>plpython2</>
+ and <application>plpython3</> (Tom Lane)
+ </para>
+
+ <para>
+ In principle, both versions of <application>PL/Python</> can be used in
+ the same database, though not in the same session (because the two
+ versions of <application>libpython</> cannot safely be used concurrently).
+ However, <application>pg_restore</> and <application>pg_upgrade</> both
+ do things that can fall foul of the same-session restriction. Work
+ around that by changing the timing of the check.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>PL/Python</> regression tests to pass with Python 3.5
+ (Peter Eisentraut)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix premature clearing of <application>libpq</>'s input buffer when
+ socket EOF is seen (Tom Lane)
+ </para>
+
+ <para>
+ This mistake caused <application>libpq</> to sometimes not report the
+ backend's final error message before reporting <quote>server closed the
+ connection unexpectedly</>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Prevent certain <application>PL/Java</> parameters from being set by
+ non-superusers (Noah Misch)
+ </para>
+
+ <para>
+ This change mitigates a <application>PL/Java</> security bug
+ (CVE-2016-0766), which was fixed in <application>PL/Java</> by marking
+ these parameters as superuser-only. To fix the security hazard for
+ sites that update <productname>PostgreSQL</> more frequently
+ than <application>PL/Java</>, make the core code aware of them also.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve <application>libpq</>'s handling of out-of-memory situations
+ (Michael Paquier, Amit Kapila, Heikki Linnakangas)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix order of arguments
+ in <application>ecpg</>-generated <literal>typedef</> statements
+ (Michael Meskes)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Use <literal>%g</> not <literal>%f</> format
+ in <application>ecpg</>'s <function>PGTYPESnumeric_from_double()</>
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <application>ecpg</>-supplied header files to not contain comments
+ continued from a preprocessor directive line onto the next line
+ (Michael Meskes)
+ </para>
+
+ <para>
+ Such a comment is rejected by <application>ecpg</>. It's not yet clear
+ whether <application>ecpg</> itself should be changed.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <function>hstore_to_json_loose()</>'s test for whether
+ an <type>hstore</> value can be converted to a JSON number (Tom Lane)
+ </para>
+
+ <para>
+ Previously this function could be fooled by non-alphanumeric trailing
+ characters, leading to emitting syntactically-invalid JSON.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure that <filename>contrib/pgcrypto</>'s <function>crypt()</>
+ function can be interrupted by query cancel (Andreas Karlsson)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Accept <application>flex</> versions later than 2.5.x
+ (Tom Lane, Michael Paquier)
+ </para>
+
+ <para>
+ Now that flex 2.6.0 has been released, the version checks in our build
+ scripts needed to be adjusted.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improve reproducibility of build output by ensuring filenames are given
+ to the linker in a fixed order (Christoph Berg)
+ </para>
+
+ <para>
+ This avoids possible bitwise differences in the produced executable
+ files from one build to the next.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Install our <filename>missing</> script where PGXS builds can find it
+ (Jim Nasby)
+ </para>
+
+ <para>
+ This allows sane behavior in a PGXS build done on a machine where build
+ tools such as <application>bison</> are missing.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Ensure that <filename>dynloader.h</> is included in the installed
+ header files in MSVC builds (Bruce Momjian, Michael Paquier)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Add variant regression test expected-output file to match behavior of
+ current <application>libxml2</> (Tom Lane)
+ </para>
+
+ <para>
+ The fix for <application>libxml2</>'s CVE-2015-7499 causes it not to
+ output error context reports in some cases where it used to do so.
+ This seems to be a bug, but we'll probably have to live with it for
+ some time, so work around it.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</> release 2016a for
+ DST law changes in Cayman Islands, Metlakatla, and Trans-Baikal
+ Territory (Zabaykalsky Krai), plus historical corrections for Pakistan.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-3-10">
<title>Release 9.3.10</title>
</para>
</listitem>
-<!--
-Branch: master [b8682a715] 2016-01-26 15:38:33 -0500
-Branch: REL9_5_STABLE [2acb682f6] 2016-01-26 15:38:33 -0500
-Branch: REL9_4_STABLE [2b3983158] 2016-01-26 15:38:33 -0500
-Branch: REL9_3_STABLE [9bbfca8fd] 2016-01-26 15:38:33 -0500
-Branch: REL9_2_STABLE [3a7af9d73] 2016-01-26 15:38:33 -0500
-Branch: REL9_1_STABLE [b043df093] 2016-01-26 15:38:33 -0500
--->
-
<listitem>
<para>
Make <literal>%h</> and <literal>%r</> escapes
</para>
</listitem>
-<!--
-Branch: master [6a61d1ff9] 2016-01-14 13:06:03 +0100
-Branch: REL9_5_STABLE [3276ca303] 2016-01-14 13:07:20 +0100
-Branch: REL9_4_STABLE [ab49f87d5] 2016-01-14 13:07:35 +0100
-Branch: REL9_3_STABLE [77d8edcf5] 2016-01-14 13:07:45 +0100
-Branch: REL9_2_STABLE [df0bd5a0f] 2016-01-14 13:07:55 +0100
-Branch: REL9_1_STABLE [b1c0f92eb] 2016-01-14 13:08:10 +0100
--->
-
<listitem>
<para>
Avoid leaking a token handle during SSPI authentication
</para>
</listitem>
-<!--
-Branch: master [7e2247047] 2016-01-29 10:28:02 +0100
-Branch: REL9_5_STABLE [56251f396] 2016-01-29 10:28:02 +0100
-Branch: REL9_4_STABLE [5849b6e32] 2016-01-29 10:28:02 +0100
-Branch: REL9_3_STABLE [db678ca16] 2016-01-29 10:28:03 +0100
-Branch: REL9_2_STABLE [a362cc2e3] 2016-01-29 10:28:03 +0100
-Branch: REL9_1_STABLE [ed5f57218] 2016-01-29 10:28:03 +0100
--->
-
<listitem>
<para>
Fix <application>psql</>'s <literal>\det</> command to interpret its
</para>
</listitem>
-<!--
-Branch: master [a96761391] 2016-01-07 11:59:08 -0300
-Branch: REL9_5_STABLE [744d01c9a] 2016-01-07 11:59:08 -0300
-Branch: REL9_4_STABLE [c7aca3d45] 2016-01-07 11:59:08 -0300
-Branch: REL9_3_STABLE [74d4009b8] 2016-01-07 11:59:08 -0300
-Branch: REL9_2_STABLE [5c4cbd5d1] 2016-01-07 11:59:08 -0300
-Branch: REL9_1_STABLE [b96f6f444] 2016-01-07 11:59:08 -0300
--->
-
<listitem>
<para>
In <application>pg_ctl</> on Windows, check service status to decide
</para>
</listitem>
-<!--
-Branch: master [e72d7d853] 2016-01-13 18:55:27 -0500
-Branch: REL9_5_STABLE [c42df2d46] 2016-01-13 18:55:27 -0500
-Branch: REL9_4_STABLE [7393208b5] 2016-01-13 18:55:27 -0500
-Branch: REL9_3_STABLE [b87403f70] 2016-01-13 18:55:27 -0500
-Branch: REL9_2_STABLE [be2b27651] 2016-01-13 18:55:27 -0500
-Branch: REL9_1_STABLE [5108013db] 2016-01-13 18:55:27 -0500
--->
-
<listitem>
<para>
Fix assorted corner-case bugs in <application>pg_dump</>'s processing
</para>
</listitem>
-<!--
-Branch: master [df43fcf45] 2016-01-22 20:04:35 -0300
-Branch: REL9_5_STABLE [1e910cf5b] 2016-01-22 20:04:35 -0300
--->
-
- <listitem>
- <para>
- Fix improper quoting of domain constraint names
- in <application>pg_dump</> (Elvis Pranskevichus)
- </para>
- </listitem>
-
-<!--
-Branch: master [0ed707e9b] 2016-02-04 00:26:10 -0500
-Branch: REL9_5_STABLE [b99dd7170] 2016-02-04 00:26:10 -0500
-Branch: REL9_4_STABLE [411e2b0d5] 2016-02-04 00:26:10 -0500
-Branch: REL9_3_STABLE [aefbc208b] 2016-02-04 00:26:10 -0500
-Branch: REL9_2_STABLE [4f58a7003] 2016-02-04 00:26:10 -0500
-Branch: REL9_1_STABLE [9c704632c] 2016-02-04 00:26:10 -0500
--->
-
<listitem>
<para>
Make <application>pg_dump</> mark a view's triggers as needing to be
</para>
</listitem>
-<!--
-Branch: master [64f5edca2] 2016-02-01 08:23:41 -0500
-Branch: REL9_5_STABLE [829757c8a] 2016-02-01 08:26:07 -0500
-Branch: REL9_4_STABLE [c33d1a8d5] 2016-02-03 09:15:29 -0500
-Branch: REL9_3_STABLE [014796aa3] 2016-02-03 09:19:58 -0500
-Branch: REL9_2_STABLE [b63a4f418] 2016-02-03 09:21:44 -0500
-Branch: REL9_1_STABLE [4c8b07d3c] 2016-02-03 09:25:34 -0500
--->
-
<listitem>
<para>
Install guards in <application>pgbench</> against corner-case overflow
</para>
</listitem>
-<!--
-Branch: master [4aecd22d3] 2016-01-05 17:25:12 -0300
-Branch: REL9_5_STABLE [7ef311eb4] 2016-01-05 17:25:12 -0300
--->
-
- <listitem>
- <para>
- Suppress useless warning message when <application>pg_receivexlog</>
- connects to a pre-9.4 server (Marco Nenciarini)
- </para>
- </listitem>
-
<!--
Branch: master [fc995bfdb] 2015-12-28 10:50:35 -0300
</para>
</listitem>
-<!--
-Branch: master [866566a69] 2016-01-11 19:55:39 -0500
-Branch: REL9_5_STABLE [db8fa56d6] 2016-01-11 19:55:39 -0500
-Branch: REL9_4_STABLE [22815752e] 2016-01-11 19:55:40 -0500
-Branch: REL9_3_STABLE [0ddeaba7e] 2016-01-11 19:55:40 -0500
-Branch: REL9_2_STABLE [3843ba510] 2016-01-11 19:55:40 -0500
-Branch: master [fb6fcbd33] 2016-01-11 20:06:36 -0500
-Branch: REL9_5_STABLE [5ef26b8de] 2016-01-11 20:06:47 -0500
--->
-
<listitem>
<para>
Avoid dump/reload problems when using both <application>plpython2</>
</para>
<para>
- In principle, both versions of PL/Python can be used in the same
- database, though not in the same session (because the two versions of
- <application>libpython</> cannot safely be used concurrently).
+ In principle, both versions of <application>PL/Python</> can be used in
+ the same database, though not in the same session (because the two
+
versions of <application>libpython</> cannot safely be used concurrently).
However, <application>pg_restore</> and <application>pg_upgrade</> both
do things that can fall foul of the same-session restriction. Work
around that by changing the timing of the check.
</para>
</listitem>
+ <listitem>
+ <para>
+ Fix <application>PL/Python</> regression tests to pass with Python 3.5
+ (Peter Eisentraut)
+ </para>
+ </listitem>
+
<!--
Branch: master [c40591885] 2015-11-12 13:03:52 -0500
Branch: REL9_5_STABLE Release: REL9_5_0 [747854f01] 2015-11-12 13:03:52 -0500
Branch: REL9_4_STABLE [40879a92b] 2015-11-12 13:03:52 -0500
Branch: REL9_3_STABLE [db6e8e162] 2015-11-12 13:03:53 -0500
--->
-
-<!--
-Branch: REL9_4_STABLE [f1b898759] 2015-11-14 13:43:43 -0500
-Branch: REL9_3_STABLE [a37ab812c] 2015-11-14 13:44:09 -0500
-Branch: REL9_2_STABLE [82076c1e4] 2015-11-14 13:53:26 -0500
-Branch: REL9_5_STABLE [a66c1fcdd] 2016-01-08 11:39:28 -0500
-->
- <listitem>
- <para>
- Fix PL/Python regression tests to pass with Python 3.5
- (Peter Eisentraut)
- </para>
- </listitem>
-
<listitem>
<para>
Fix premature clearing of <application>libpq</>'s input buffer when
</para>
</listitem>
+ <listitem>
+ <para>
+ Prevent certain <application>PL/Java</> parameters from being set by
+ non-superusers (Noah Misch)
+ </para>
+
+ <para>
+ This change mitigates a <application>PL/Java</> security bug
+ (CVE-2016-0766), which was fixed in <application>PL/Java</> by marking
+ these parameters as superuser-only. To fix the security hazard for
+ sites that update <productname>PostgreSQL</> more frequently
+ than <application>PL/Java</>, make the core code aware of them also.
+ </para>
+ </listitem>
+
<!--
Branch: master [7b96bf445] 2015-12-14 18:19:10 +0200
</para>
</listitem>
-<!--
-Branch: master [7a58d19b0] 2016-02-01 13:21:00 +0100
-Branch: REL9_5_STABLE [40482e606] 2016-02-01 13:20:37 +0100
-Branch: REL9_3_STABLE [0b55fef39] 2016-02-01 13:19:10 +0100
-Branch: REL9_2_STABLE [d9ce5d201] 2016-02-01 13:19:34 +0100
-Branch: REL9_1_STABLE [79782b407] 2016-02-01 13:19:43 +0100
--->
-
<listitem>
<para>
Fix <application>ecpg</>-supplied header files to not contain comments
</para>
</listitem>
-<!--
-Branch: master [e6ecc93a1] 2016-02-03 01:39:48 -0500
-Branch: REL9_5_STABLE [1c291624b] 2016-02-03 01:39:08 -0500
-Branch: REL9_4_STABLE [aa223a037] 2016-02-03 01:39:08 -0500
-Branch: REL9_3_STABLE [1f2b195eb] 2016-02-03 01:39:08 -0500
--->
-
<listitem>
<para>
Fix <function>hstore_to_json_loose()</>'s test for whether
</para>
</listitem>
-<!--
-Branch: master [9418d79a7] 2016-02-04 21:17:53 -0500
-Branch: REL9_5_STABLE [453d40817] 2016-02-04 21:17:46 -0500
-Branch: REL9_4_STABLE [1f3294c22] 2016-02-04 21:15:57 -0500
-Branch: master [37c84570b] 2016-02-04 22:27:13 -0500
-Branch: REL9_5_STABLE [d160e2a34] 2016-02-04 22:27:38 -0500
-Branch: REL9_4_STABLE [2099b911d] 2016-02-04 22:27:47 -0500
--->
-
<listitem>
<para>
In <filename>contrib/postgres_fdw</>, fix bugs triggered by use
</para>
</listitem>
-<!--
-Branch: master [a396144ac] 2016-01-22 11:53:06 -0500
-Branch: REL9_5_STABLE [47acf3add] 2016-01-22 11:53:06 -0500
--->
-
- <listitem>
- <para>
- Fix ill-advised restriction of <literal>NAMEDATALEN</> to be less
- than 256 (Robert Haas, Tom Lane)
- </para>
- </listitem>
-
-<!--
-Branch: master [3343ea9e8] 2016-01-05 15:47:05 -0500
-Branch: REL9_5_STABLE [8805af088] 2016-01-05 15:47:05 -0500
-Branch: REL9_4_STABLE [8c558b2e9] 2016-01-05 15:47:05 -0500
-Branch: REL9_3_STABLE [6d899f098] 2016-01-05 15:47:05 -0500
--->
-
<listitem>
<para>
Improve reproducibility of build output by ensuring filenames are given
</para>
</listitem>
-<!--
-Branch: master [216d56843] 2016-01-19 23:30:29 -0500
-Branch: REL9_5_STABLE [34bda20ae] 2016-01-19 23:30:29 -0500
-Branch: REL9_4_STABLE [8b3d52801] 2016-01-19 23:30:29 -0500
-Branch: REL9_3_STABLE [7a47262ce] 2016-01-19 23:30:28 -0500
-Branch: REL9_2_STABLE [49d65e857] 2016-01-19 23:30:28 -0500
-Branch: REL9_1_STABLE [b1bc38144] 2016-01-19 23:30:28 -0500
--->
-
<listitem>
<para>
Ensure that <filename>dynloader.h</> is included in the installed
- header files in MSVC builds (Michael Paquier)
+ header files in MSVC builds (Bruce Momjian, Michael Paquier)
</para>
</listitem>
</para>
</listitem>
-<!--
-Branch: master [a73311e52] 2016-02-05 10:59:09 -0500
-Branch: REL9_5_STABLE [37e694632] 2016-02-05 10:59:21 -0500
-Branch: REL9_4_STABLE [31b792f61] 2016-02-05 10:59:26 -0500
-Branch: REL9_3_STABLE [9a3475b84] 2016-02-05 10:59:31 -0500
-Branch: REL9_2_STABLE [32f17a2e7] 2016-02-05 10:59:35 -0500
-Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
--->
-
<listitem>
<para>
Update time zone data files to <application>tzdata</> release 2016a for
<!-- doc/src/sgml/release-9.5.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-5-1">
+ <title>Release 9.5.1</title>
+
+ <note>
+ <title>Release Date</title>
+ <simpara>2016-02-11</simpara>
+ </note>
+
+ <para>
+ This release contains a variety of fixes from 9.5.0.
+ 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.1</title>
+
+ <para>
+ A dump/restore is not required for those running 9.5.X.
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+<!--
+Branch: master [f867ce551] 2016-02-07 12:29:32 -0500
+Branch: REL9_5_STABLE [129db3cbe] 2016-02-07 12:29:17 -0500
+-->
+
+ <listitem>
+ <para>
+ Fix an oversight that caused hash joins to miss joining to some tuples
+ of the inner relation in rare cases (Tomas Vondra, Tom Lane)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [b8682a715] 2016-01-26 15:38:33 -0500
+Branch: REL9_5_STABLE [2acb682f6] 2016-01-26 15:38:33 -0500
+Branch: REL9_4_STABLE [2b3983158] 2016-01-26 15:38:33 -0500
+Branch: REL9_3_STABLE [9bbfca8fd] 2016-01-26 15:38:33 -0500
+Branch: REL9_2_STABLE [3a7af9d73] 2016-01-26 15:38:33 -0500
+Branch: REL9_1_STABLE [b043df093] 2016-01-26 15:38:33 -0500
+-->
+
+ <listitem>
+ <para>
+ Make <literal>%h</> and <literal>%r</> escapes
+ in <varname>log_line_prefix</> work for messages emitted due
+ to <varname>log_connections</> (Tom Lane)
+ </para>
+
+ <para>
+ Previously, <literal>%h</>/<literal>%r</> started to work just after a
+ new session had emitted the <quote>connection received</> log message;
+ now they work for that message too.
+ </para>
+ </listitem>
+
+<!--
+Branch: master [6a61d1ff9] 2016-01-14 13:06:03 +0100
+Branch: REL9_5_STABLE [3276ca303] 2016-01-14 13:07:20 +0100
+Branch: REL9_4_STABLE [ab49f87d5] 2016-01-14 13:07:35 +0100
+Branch: REL9_3_STABLE [77d8edcf5] 2016-01-14 13:07:45 +0100
+Branch: REL9_2_STABLE [df0bd5a0f] 2016-01-14 13:07:55 +0100
+Branch: REL9_1_STABLE [b1c0f92eb] 2016-01-14 13:08:10 +0100
+-->
+
+ <listitem>
+ <para>
+ Avoid leaking a token handle during SSPI authentication
+ (Christian Ullrich)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [7e2247047] 2016-01-29 10:28:02 +0100
+Branch: REL9_5_STABLE [56251f396] 2016-01-29 10:28:02 +0100
+Branch: REL9_4_STABLE [5849b6e32] 2016-01-29 10:28:02 +0100
+Branch: REL9_3_STABLE [db678ca16] 2016-01-29 10:28:03 +0100
+Branch: REL9_2_STABLE [a362cc2e3] 2016-01-29 10:28:03 +0100
+Branch: REL9_1_STABLE [ed5f57218] 2016-01-29 10:28:03 +0100
+-->
+
+ <listitem>
+ <para>
+ Fix <application>psql</>'s <literal>\det</> command to interpret its
+ pattern argument the same way as other <literal>\d</> commands with
+ potentially schema-qualified patterns do (Reece Hart)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [a96761391] 2016-01-07 11:59:08 -0300
+Branch: REL9_5_STABLE [744d01c9a] 2016-01-07 11:59:08 -0300
+Branch: REL9_4_STABLE [c7aca3d45] 2016-01-07 11:59:08 -0300
+Branch: REL9_3_STABLE [74d4009b8] 2016-01-07 11:59:08 -0300
+Branch: REL9_2_STABLE [5c4cbd5d1] 2016-01-07 11:59:08 -0300
+Branch: REL9_1_STABLE [b96f6f444] 2016-01-07 11:59:08 -0300
+-->
+
+ <listitem>
+ <para>
+ In <application>pg_ctl</> on Windows, check service status to decide
+ where to send output, rather than checking if standard output is a
+ terminal (Michael Paquier)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [e72d7d853] 2016-01-13 18:55:27 -0500
+Branch: REL9_5_STABLE [c42df2d46] 2016-01-13 18:55:27 -0500
+Branch: REL9_4_STABLE [7393208b5] 2016-01-13 18:55:27 -0500
+Branch: REL9_3_STABLE [b87403f70] 2016-01-13 18:55:27 -0500
+Branch: REL9_2_STABLE [be2b27651] 2016-01-13 18:55:27 -0500
+Branch: REL9_1_STABLE [5108013db] 2016-01-13 18:55:27 -0500
+-->
+
+ <listitem>
+ <para>
+ Fix assorted corner-case bugs in <application>pg_dump</>'s processing
+ of extension member objects (Tom Lane)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [df43fcf45] 2016-01-22 20:04:35 -0300
+Branch: REL9_5_STABLE [1e910cf5b] 2016-01-22 20:04:35 -0300
+-->
+
+ <listitem>
+ <para>
+ Fix improper quoting of domain constraint names
+ in <application>pg_dump</> (Elvis Pranskevichus)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [0ed707e9b] 2016-02-04 00:26:10 -0500
+Branch: REL9_5_STABLE [b99dd7170] 2016-02-04 00:26:10 -0500
+Branch: REL9_4_STABLE [411e2b0d5] 2016-02-04 00:26:10 -0500
+Branch: REL9_3_STABLE [aefbc208b] 2016-02-04 00:26:10 -0500
+Branch: REL9_2_STABLE [4f58a7003] 2016-02-04 00:26:10 -0500
+Branch: REL9_1_STABLE [9c704632c] 2016-02-04 00:26:10 -0500
+-->
+
+ <listitem>
+ <para>
+ Make <application>pg_dump</> mark a view's triggers as needing to be
+ processed after its rule, to prevent possible failure during
+ parallel <application>pg_restore</> (Tom Lane)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [64f5edca2] 2016-02-01 08:23:41 -0500
+Branch: REL9_5_STABLE [829757c8a] 2016-02-01 08:26:07 -0500
+Branch: REL9_4_STABLE [c33d1a8d5] 2016-02-03 09:15:29 -0500
+Branch: REL9_3_STABLE [014796aa3] 2016-02-03 09:19:58 -0500
+Branch: REL9_2_STABLE [b63a4f418] 2016-02-03 09:21:44 -0500
+Branch: REL9_1_STABLE [4c8b07d3c] 2016-02-03 09:25:34 -0500
+-->
+
+ <listitem>
+ <para>
+ Install guards in <application>pgbench</> against corner-case overflow
+ conditions during evaluation of script-specified division or modulo
+ operators (Fabien Coelho, Michael Paquier)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [4aecd22d3] 2016-01-05 17:25:12 -0300
+Branch: REL9_5_STABLE [7ef311eb4] 2016-01-05 17:25:12 -0300
+-->
+
+ <listitem>
+ <para>
+ Suppress useless warning message when <application>pg_receivexlog</>
+ connects to a pre-9.4 server (Marco Nenciarini)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [866566a69] 2016-01-11 19:55:39 -0500
+Branch: REL9_5_STABLE [db8fa56d6] 2016-01-11 19:55:39 -0500
+Branch: REL9_4_STABLE [22815752e] 2016-01-11 19:55:40 -0500
+Branch: REL9_3_STABLE [0ddeaba7e] 2016-01-11 19:55:40 -0500
+Branch: REL9_2_STABLE [3843ba510] 2016-01-11 19:55:40 -0500
+Branch: master [fb6fcbd33] 2016-01-11 20:06:36 -0500
+Branch: REL9_5_STABLE [5ef26b8de] 2016-01-11 20:06:47 -0500
+-->
+
+ <listitem>
+ <para>
+ Avoid dump/reload problems when using both <application>plpython2</>
+ and <application>plpython3</> (Tom Lane)
+ </para>
+
+ <para>
+ In principle, both versions of <application>PL/Python</> can be used in
+ the same database, though not in the same session (because the two
+ versions of <application>libpython</> cannot safely be used concurrently).
+ However, <application>pg_restore</> and <application>pg_upgrade</> both
+ do things that can fall foul of the same-session restriction. Work
+ around that by changing the timing of the check.
+ </para>
+ </listitem>
+
+<!--
+Branch: REL9_4_STABLE [f1b898759] 2015-11-14 13:43:43 -0500
+Branch: REL9_3_STABLE [a37ab812c] 2015-11-14 13:44:09 -0500
+Branch: REL9_2_STABLE [82076c1e4] 2015-11-14 13:53:26 -0500
+Branch: REL9_5_STABLE [a66c1fcdd] 2016-01-08 11:39:28 -0500
+-->
+
+ <listitem>
+ <para>
+ Fix <application>PL/Python</> regression tests to pass with Python 3.5
+ (Peter Eisentraut)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [f4aa3a18a] 2016-02-05 20:22:51 -0500
+Branch: REL9_5_STABLE [0089dd34a] 2016-02-05 20:23:04 -0500
+Branch: REL9_4_STABLE [ed6deeb7a] 2016-02-05 20:23:07 -0500
+Branch: REL9_3_STABLE [34e91736b] 2016-02-05 20:23:11 -0500
+Branch: REL9_2_STABLE [de9766d39] 2016-02-05 20:23:14 -0500
+Branch: REL9_1_STABLE [b1f591c50] 2016-02-05 20:23:19 -0500
+-->
+
+ <listitem>
+ <para>
+ Prevent certain <application>PL/Java</> parameters from being set by
+ non-superusers (Noah Misch)
+ </para>
+
+ <para>
+ This change mitigates a <application>PL/Java</> security bug
+ (CVE-2016-0766), which was fixed in <application>PL/Java</> by marking
+ these parameters as superuser-only. To fix the security hazard for
+ sites that update <productname>PostgreSQL</> more frequently
+ than <application>PL/Java</>, make the core code aware of them also.
+ </para>
+ </listitem>
+
+<!--
+Branch: master [7a58d19b0] 2016-02-01 13:21:00 +0100
+Branch: REL9_5_STABLE [40482e606] 2016-02-01 13:20:37 +0100
+Branch: REL9_3_STABLE [0b55fef39] 2016-02-01 13:19:10 +0100
+Branch: REL9_2_STABLE [d9ce5d201] 2016-02-01 13:19:34 +0100
+Branch: REL9_1_STABLE [79782b407] 2016-02-01 13:19:43 +0100
+-->
+
+ <listitem>
+ <para>
+ Fix <application>ecpg</>-supplied header files to not contain comments
+ continued from a preprocessor directive line onto the next line
+ (Michael Meskes)
+ </para>
+
+ <para>
+ Such a comment is rejected by <application>ecpg</>. It's not yet clear
+ whether <application>ecpg</> itself should be changed.
+ </para>
+ </listitem>
+
+<!--
+Branch: master [e6ecc93a1] 2016-02-03 01:39:48 -0500
+Branch: REL9_5_STABLE [1c291624b] 2016-02-03 01:39:08 -0500
+Branch: REL9_4_STABLE [aa223a037] 2016-02-03 01:39:08 -0500
+Branch: REL9_3_STABLE [1f2b195eb] 2016-02-03 01:39:08 -0500
+-->
+
+ <listitem>
+ <para>
+ Fix <function>hstore_to_json_loose()</>'s test for whether
+ an <type>hstore</> value can be converted to a JSON number (Tom Lane)
+ </para>
+
+ <para>
+ Previously this function could be fooled by non-alphanumeric trailing
+ characters, leading to emitting syntactically-invalid JSON.
+ </para>
+ </listitem>
+
+<!--
+Branch: master [9418d79a7] 2016-02-04 21:17:53 -0500
+Branch: REL9_5_STABLE [453d40817] 2016-02-04 21:17:46 -0500
+Branch: REL9_4_STABLE [1f3294c22] 2016-02-04 21:15:57 -0500
+Branch: master [37c84570b] 2016-02-04 22:27:13 -0500
+Branch: REL9_5_STABLE [d160e2a34] 2016-02-04 22:27:38 -0500
+Branch: REL9_4_STABLE [2099b911d] 2016-02-04 22:27:47 -0500
+-->
+
+ <listitem>
+ <para>
+ In <filename>contrib/postgres_fdw</>, fix bugs triggered by use
+ of <literal>tableoid</> in data-modifying commands (Etsuro Fujita,
+ Robert Haas)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [a396144ac] 2016-01-22 11:53:06 -0500
+Branch: REL9_5_STABLE [47acf3add] 2016-01-22 11:53:06 -0500
+-->
+
+ <listitem>
+ <para>
+ Fix ill-advised restriction of <literal>NAMEDATALEN</> to be less
+ than 256 (Robert Haas, Tom Lane)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [3343ea9e8] 2016-01-05 15:47:05 -0500
+Branch: REL9_5_STABLE [8805af088] 2016-01-05 15:47:05 -0500
+Branch: REL9_4_STABLE [8c558b2e9] 2016-01-05 15:47:05 -0500
+Branch: REL9_3_STABLE [6d899f098] 2016-01-05 15:47:05 -0500
+-->
+
+ <listitem>
+ <para>
+ Improve reproducibility of build output by ensuring filenames are given
+ to the linker in a fixed order (Christoph Berg)
+ </para>
+
+ <para>
+ This avoids possible bitwise differences in the produced executable
+ files from one build to the next.
+ </para>
+ </listitem>
+
+<!--
+Branch: master [216d56843] 2016-01-19 23:30:29 -0500
+Branch: REL9_5_STABLE [34bda20ae] 2016-01-19 23:30:29 -0500
+Branch: REL9_4_STABLE [8b3d52801] 2016-01-19 23:30:29 -0500
+Branch: REL9_3_STABLE [7a47262ce] 2016-01-19 23:30:28 -0500
+Branch: REL9_2_STABLE [49d65e857] 2016-01-19 23:30:28 -0500
+Branch: REL9_1_STABLE [b1bc38144] 2016-01-19 23:30:28 -0500
+-->
+
+ <listitem>
+ <para>
+ Ensure that <filename>dynloader.h</> is included in the installed
+ header files in MSVC builds (Bruce Momjian, Michael Paquier)
+ </para>
+ </listitem>
+
+<!--
+Branch: master [a73311e52] 2016-02-05 10:59:09 -0500
+Branch: REL9_5_STABLE [37e694632] 2016-02-05 10:59:21 -0500
+Branch: REL9_4_STABLE [31b792f61] 2016-02-05 10:59:26 -0500
+Branch: REL9_3_STABLE [9a3475b84] 2016-02-05 10:59:31 -0500
+Branch: REL9_2_STABLE [32f17a2e7] 2016-02-05 10:59:35 -0500
+Branch: REL9_1_STABLE [6887d72d0] 2016-02-05 10:59:39 -0500
+-->
+
+ <listitem>
+ <para>
+ Update time zone data files to <application>tzdata</> release 2016a for
+ DST law changes in Cayman Islands, Metlakatla, and Trans-Baikal
+ Territory (Zabaykalsky Krai), plus historical corrections for Pakistan.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-5">
<title>Release 9.5</title>
projects / postgresql.git / commitdiff