Appendix E. Release Notes
Fixclienthostname lookupwhen processing
entries that specifyhost namesinstead
of IP addresses (Tom Lane)
Ensure that reverse-DNS lookup failures are reported, instead of just silently not matching such
entries. Also ensure that we make only one reverse-DNS lookup attempt per connection, not one
per host name entry, which is what previously happened if the lookup attempts failed.
Allow the root user to use
postgres -C variable
The prohibition on starting the server as root does not need to extend to these operations, and
relaxing it prevents failure of pg_ctl insome scenarios.
Secure Unix-domain sockets of temporary postmasters started during
Any local user able to access the socket ﬁle could connect as the server’s bootstrap superuser, then
proceed to execute arbitrary code as the operating-system user running the test, as we previously
noted in CVE-2014-0067. This change defends against that risk by placing the server’s socket in
atemporary, mode 0700 subdirectory of
.The hazard remains however on platforms where
Unix sockets are not supported, notably Windows, because then the temporary postmaster must
accept local TCP connections.
Auseful side effect of this change is to simplify
testing in builds that override
.Popular non-default values like
writable by the build user, requiring workarounds that will no longer be necessary.
Fix tablespace creationWAL replay to work on Windows (MauMau)
Fix detection of socket creation failures on Windows (Bruce Momjian)
On Windows, allow new sessions to absorb values of PGC_BACKEND parameters (such as
log_connections) from the conﬁguration ﬁle (Amit Kapila)
Previously, if such a parameter were changed in the ﬁle post-startup, the change would have no
Properly quote executable path names on Windows (Nikhil Deshpande)
This oversight could cause initdb and pg_upgrade to fail on Windows, if the installation path con-
tainedboth spaces and
Fix linking of libpython on OS X (Tom Lane)
The method we previously used can fail with the Pythonlibrary supplied by Xcode 5.0 and later.
Avoid buffer bloatin libpqwhenthe server consistently sends data faster than the client can absorb
it (Shin-ichi Morita, Tom Lane)
libpq could be coerced into enlarging its input buffer until it runs out of memory (which would
be reported misleadingly as “lost synchronization with server”). Under ordinary circumstances
it’s quite far-fetched that data could be continuously transmitted more quickly than the
loop can absorb it, but this has been observed when the client is artiﬁcially slowed by scheduler
Ensure that LDAP lookup attempts in libpq time out as intended (Laurenz Albe)
Fix ecpg to do the right thing when an array of
is the target for a FETCH statement
returning more than one row, as well as some other array-handling ﬁxes (Ashutosh Bapat)
Fix pg_dump to cope with a materialized view that depends on a table’s primary key (Tom Lane)
This occurs if the view’s query relies on functional dependency to abbreviate a
pg_dump got sufﬁciently confused that it dumped the materialized view as a regular view.