This change prevents problems when there are multiple
connections using OpenSSL within a single process and not all the
code involved follows the same rules for when to clear the error
queue. Failures have been reported specifically when a client
application uses SSL connections in libpq concurrently with SSL connections using
the PHP, Python, or Ruby wrappers for OpenSSL. It's possible for
similar problems to arise within the server as well, if an
extension module establishes an outgoing SSL connection.

Fix "failed to build any N-way joins" planner error with a full
join enclosed in the right-hand side of a left join (Tom Lane)

Given a three-or-more-way equivalence class of variables, such
as X.X = Y.Y = Z.Z, it was possible for
the planner to omit some of the tests needed to enforce that all
the variables are actually equal, leading to join rows being output
that didn't satisfy the WHERE clauses. For
various reasons, erroneous plans were seldom selected in practice,
so that this bug has gone undetected for a long time.

In such a case, the operator family was restored into the new
database, but it was no longer marked as part of the extension.
This had no immediate ill effects, but would cause later
pg_dump runs to emit output that
would cause (harmless) errors on restore.

These changes were not originally needed in pre-9.4 branches,
but we recently back-patched a fix that expected the barrier code
to work properly. Only IA64 (when using icc), HPPA, and Alpha
platforms are affected.

Reduce the number of SysV semaphores used by a build configured
with --disable-spinlocks (Tom Lane)

Use the FORMAT_MESSAGE_IGNORE_INSERTS
flag where appropriate. No live bug is known to exist here, but it
seems like a good idea to be careful.

Update time zone data files to tzdata release 2016d for DST law changes in
Russia and Venezuela. There are new zone names Europe/Kirov and Asia/Tomsk
to reflect the fact that these regions now have different time zone
histories from adjacent regions.

Submit correction

If you see anything in the documentation that is not correct, does not match
your experience with the particular feature or requires further clarification,
please use
this form
to report a documentation issue.