diff --git a/doc/src/sgml/release-9.6.sgml b/doc/src/sgml/release-9.6.sgml
index dc7b4793873..cdff0849eac 100644
--- a/doc/src/sgml/release-9.6.sgml
+++ b/doc/src/sgml/release-9.6.sgml
@@ -1,6 +1,908 @@
+
+ Release 9.6.3
+
+
+ Release Date
+ 2017-05-11
+
+
+
+ This release contains a variety of fixes from 9.6.2.
+ For information about new features in the 9.6 major release, see
+ .
+
+
+
+ Migration to Version 9.6.3
+
+
+ A dump/restore is not required for those running 9.6.X.
+
+
+
+ However, if you are upgrading from a version earlier than 9.6.2,
+ see .
+
+
+
+
+ Changes
+
+
+
+
+
+
+ Fix possible corruption of init forks of unlogged indexes
+ (Robert Haas, Michael Paquier)
+
+
+
+ This could result in an unlogged index being set to an invalid state
+ after a crash and restart. Such a problem would persist until the
+ index was dropped and rebuilt.
+
+
+
+
+
+
+ Fix incorrect reconstruction of pg_subtrans entries
+ when a standby server replays a prepared but uncommitted two-phase
+ transaction (Tom Lane)
+
+
+
+ In most cases this turned out to have no visible ill effects, but in
+ corner cases it could result in circular references
+ in pg_subtrans, potentially causing infinite loops
+ in queries that examine rows modified by the two-phase transaction.
+
+
+
+
+
+
+ Fix possibly-corrupt initial snapshot during logical decoding
+ (Petr Jelinek, Andres Freund)
+
+
+
+ If a logical decoding replication slot was created while another slot
+ already exists, it was initialized with a potentially-corrupted
+ snapshot, allowing wrong data to be returned during decoding.
+ The time window during which this snapshot continued to be used
+ depended on how busy the server was; under low load it would be hard
+ to see any problem.
+
+
+
+
+
+
+ Avoid possible crash in walsender due to failure
+ to initialize a string buffer (Stas Kelvich, Fujii Masao)
+
+
+
+
+
+
+ Fix possible crash when rescanning a nearest-neighbor index-only scan
+ on a GiST index (Tom Lane)
+
+
+
+
+
+
+ Prevent delays in postmaster's launching of parallel worker processes
+ (Tom Lane)
+
+
+
+ There could be a significant delay (up to tens of seconds) before
+ satisfying a query's request for more than one worker process. On most
+ platforms this required unlucky timing, but on some it was the typical
+ case.
+
+
+
+
+
+
+ Fix postmaster's handling of fork() failure for a
+ background worker process (Tom Lane)
+
+
+
+ Previously, the postmaster partially updated its state as though
+ the process had been successfully launched, resulting in subsequent
+ confusion.
+
+
+
+
+
+
+ Fix crash or wrong answers when a GROUPING SETS column's
+ data type is hashable but not sortable (Pavan Deolasee)
+
+
+
+
+
+
+ Fix possible no relation entry for relid 0 error when
+ planning nested set operations (Tom Lane)
+
+
+
+
+
+
+ Fix assorted minor issues in planning of parallel queries (Robert Haas)
+
+
+
+
+
+
+ Avoid applying physical targetlist optimization to custom
+ scans (Dmitry Ivanov, Tom Lane)
+
+
+
+ This optimization supposed that retrieving all columns of a tuple
+ is inexpensive, which is true for ordinary Postgres tuples; but it
+ might not be the case at all for a custom scan provider.
+
+
+
+
+
+
+ Ensure parsing of queries in extension scripts sees the results of
+ immediately-preceding DDL (Julien Rouhaud, Tom Lane)
+
+
+
+ Due to lack of a cache flush step between commands in an extension
+ script file, non-utility queries might not see the effects of an
+ immediately preceding catalog change, such as ALTER TABLE
+ ... RENAME.
+
+
+
+
+
+
+ Skip tablespace privilege checks when ALTER TABLE ... ALTER
+ COLUMN TYPE rebuilds an existing index (Noah Misch)
+
+
+
+ The command failed if the calling user did not currently have
+ privileges to use the tablespace an index had been created in.
+ That behavior seems unhelpful, so skip the check, allowing the
+ index to be rebuilt where it is.
+
+
+
+
+
+
+ Fix ALTER TABLE ... VALIDATE CONSTRAINT to not recurse
+ to child tables if the constraint is marked NO INHERIT
+ (Amit Langote)
+
+
+
+ This fix prevents unwanted constraint does not exist failures
+ when no matching constraint is present in the child tables.
+
+
+
+
+
+
+ Avoid dangling pointer in COPY ... TO when row-level
+ security is active for the source table (Tom Lane)
+
+
+
+ Usually this had no ill effects, but sometimes it would cause
+ unexpected errors or crashes.
+
+
+
+
+
+
+ Avoid accessing an already-closed relcache entry in CLUSTER
+ and VACUUM FULL (Tom Lane)
+
+
+
+ With some bad luck, this could lead to indexes on the target
+ relation getting rebuilt with the wrong persistence setting.
+
+
+
+
+
+
+ Fix VACUUM to account properly for pages that could not
+ be scanned due to conflicting page pins (Andrew Gierth)
+
+
+
+ This tended to lead to underestimation of the number of tuples in
+ the table. In the worst case of a small heavily-contended
+ table, VACUUM could incorrectly report that the table
+ contained no tuples, leading to very bad planning choices.
+
+
+
+
+
+
+ Ensure that bulk-tuple-transfer loops within a hash join are
+ interruptible by query cancel requests (Tom Lane, Thomas Munro)
+
+
+
+
+
+
+ Fix incorrect support for certain box operators in SP-GiST
+ (Nikita Glukhov)
+
+
+
+ SP-GiST index scans using the operators &<
+ &> &<| and |&>
+ would yield incorrect answers.
+
+
+
+
+
+
+ Fix integer-overflow problems in interval comparison (Kyotaro
+ Horiguchi and Tom Lane)
+
+
+
+ The comparison operators for type interval could yield wrong
+ answers for intervals larger than about 296000 years. Indexes on
+ columns containing such large values should be reindexed, since they
+ may be corrupt.
+
+
+
+
+
+
+ Fix cursor_to_xml() to produce valid output
+ with tableforest = false
+ (Thomas Munro, Peter Eisentraut)
+
+
+
+ Previously it failed to produce a wrapping <table>
+ element.
+
+
+
+
+
+
+ Fix roundoff problems in float8_timestamptz()
+ and make_interval() (Tom Lane)
+
+
+
+ These functions truncated, rather than rounded, when converting a
+ floating-point value to integer microseconds; that could cause
+ unexpectedly off-by-one results.
+
+
+
+
+
+
+ Fix pg_get_object_address() to handle members of operator
+ families correctly (Álvaro Herrera)
+
+
+
+
+
+
+ Fix cancelling of pg_stop_backup() when attempting to stop
+ a non-exclusive backup (Michael Paquier, David Steele)
+
+
+
+ If pg_stop_backup() was cancelled while waiting for a
+ non-exclusive backup to end, related state was left inconsistent;
+ a new exclusive backup could not be started, and there were other minor
+ problems.
+
+
+
+
+
+
+ Improve performance of pg_timezone_names view (Tom Lane)
+
+
+
+
+
+
+ Reduce memory management overhead for contexts containing many large
+ blocks (Tom Lane)
+
+
+
+
+
+
+ Fix sloppy handling of corner-case errors from lseek()
+ and close() (Tom Lane)
+
+
+
+ Neither of these system calls are likely to fail in typical situations,
+ but if they did, fd.c could get quite confused.
+
+
+
+
+
+
+ Fix incorrect check for whether postmaster is running as a Windows
+ service (Michael Paquier)
+
+
+
+ This could result in attempting to write to the event log when that
+ isn't accessible, so that no logging happens at all.
+
+
+
+
+
+
+ Fix ecpg to support COMMIT PREPARED
+ and ROLLBACK PREPARED (Masahiko Sawada)
+
+
+
+
+
+
+ Fix a double-free error when processing dollar-quoted string literals
+ in ecpg (Michael Meskes)
+
+
+
+
+
+
+ Fix pgbench to handle the combination
+ of
+
+
+
+
+
+ Fix pgbench to honor the long-form option
+ spelling
+
+
+
+
+
+ Fix pg_dump/pg_restore to correctly
+ handle privileges for the public schema when
+ using
+
+
+ Other schemas start out with no privileges granted,
+ but public does not; this requires special-case treatment
+ when it is dropped and restored due to the
+
+
+
+
+
+ In pg_dump, fix incorrect schema and owner marking for
+ comments and security labels of some types of database objects
+ (Giuseppe Broccolo, Tom Lane)
+
+
+
+ In simple cases this caused no ill effects; but for example, a
+ schema-selective restore might omit comments it should include, because
+ they were not marked as belonging to the schema of their associated
+ object.
+
+
+
+
+
+
+ Fix typo in pg_dump's query for initial privileges
+ of a procedural language (Peter Eisentraut)
+
+
+
+ This resulted in pg_dump always thinking that the
+ language had no initial privileges; since that's true for most
+ procedural languages, bad effects from this bug are probably rare.
+
+
+
+
+
+
+ Avoid emitting an invalid list file in pg_restore -l
+ when SQL object names contain newlines (Tom Lane)
+
+
+
+ Replace newlines by spaces, which is sufficient to make the output
+ valid for pg_restore -L's purposes.
+
+
+
+
+
+
+ Fix pg_upgrade to transfer comments and security labels
+ attached to large objects (blobs) (Stephen Frost)
+
+
+
+ Previously, blobs were correctly transferred to the new database, but
+ any comments or security labels attached to them were lost.
+
+
+
+
+
+
+ Improve error handling
+ in contrib/adminpack's pg_file_write()
+ function (Noah Misch)
+
+
+
+ Notably, it failed to detect errors reported
+ by fclose().
+
+
+
+
+
+
+ In contrib/dblink, avoid connection leak when establishing
+ a new unnamed connection (Joe Conway)
+
+
+
+
+
+
+ Fix contrib/pg_trgm's extraction of trigrams from regular
+ expressions (Tom Lane)
+
+
+
+ In some cases it would produce a broken data structure that could never
+ match anything, leading to GIN or GiST indexscans that use a trigram
+ index not finding any matches to the regular expression.
+
+
+
+
+
+
+ In contrib/postgres_fdw, allow join conditions that
+ contain shippable extension-provided functions to be pushed to the
+ remote server (David Rowley, Ashutosh Bapat)
+
+
+
+
+
+
+ Support OpenSSL 1.1.0 (Heikki Linnakangas, Andreas Karlsson, Tom Lane)
+
+
+
+ This is a back-patch of work previously done in newer branches;
+ it's needed since many platforms are adopting newer OpenSSL versions.
+
+
+
+
+
+
+ Support Tcl 8.6 in MSVC builds (Álvaro Herrera)
+
+
+
+
+
+
+ Sync our copy of the timezone library with IANA release tzcode2017b
+ (Tom Lane)
+
+
+
+ This fixes a bug affecting some DST transitions in January 2038.
+
+
+
+
+
+
+ Update time zone data files to tzdata release 2017b
+ for DST law changes in Chile, Haiti, and Mongolia, plus historical
+ corrections for Ecuador, Kazakhstan, Liberia, and Spain.
+ Switch to numeric abbreviations for numerous time zones in South
+ America, the Pacific and Indian oceans, and some Asian and Middle
+ Eastern countries.
+
+
+
+ The IANA time zone database previously provided textual abbreviations
+ for all time zones, sometimes making up abbreviations that have little
+ or no currency among the local population. They are in process of
+ reversing that policy in favor of using numeric UTC offsets in zones
+ where there is no evidence of real-world use of an English
+ abbreviation. At least for the time being, PostgreSQL
+ will continue to accept such removed abbreviations for timestamp input.
+ But they will not be shown in the pg_timezone_names
+ view nor used for output.
+
+
+
+
+
+
+
+
Release 9.6.2