CVS Commit History:

Log message:
postgresNN: updated to the latest
The PostgreSQL Global Development Group has released an update to all supported \
versions of our database system, including 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, \
and 9.3.25. This release fixes one security issue as well as bugs reported over \
the last three months.
All users using the affected versions of PostgreSQL should update as soon as \
possible. Please see the notes on "Updating" below for any post-update \
steps that may be required if you are using pg_stat_statements in your \
installation.
This update is also the final release for PostgreSQL 9.3, which is now \
end-of-life and will no longer receive any bug or security fixes. If your \
environment still uses PostgreSQL 9.3, please make plans to update to a \
community supported version as soon as possible. Please see our versioning \
policy for more information.
Security Issues
One security vulnerability has been closed by this release:
CVE-2018-16850: SQL injection in pg_upgrade and pg_dump, via CREATE TRIGGER ... \
REFERENCING.
Versions Affected: 10, 11
Using a purpose-crafted trigger definition, an attacker can run arbitrary SQL \
statements with superuser privileges when a superuser runs pg_upgrade on the \
database or during a pg_dump dump/restore cycle. This attack requires a CREATE \
privilege on some non-temporary schema or a TRIGGER privilege on a table. This \
is exploitable in the default PostgreSQL configuration, where all users have \
CREATE privilege on public schema.
Bug Fixes and Improvements
This update also fixes numerous bugs that were reported in the last several \
months. Some of these issues affect only version 11, but many affect all \
supported versions.
These releases include fixes that:
Ensure that automatically created child indexes are created in the same \
tablespace as the parent partitioned index
Fix several crashes with triggers
Fix problems with applying ON COMMIT DELETE ROWS to a partitioned temporary table
Fix how NULL values are handled when using LEFT JOIN with a parallelized hash join
Several fixes around using named or defaulted arguments in CALL statements
Fix for strict aggregate functions (i.e. aggregates that cannot accept NULL \
inputs) with ORDER BY columns that enforces the strictness check
Fix with CASE statements where an expression was cast to an array type
Disable an optimization for updating expression indexes in order to prevent a crash
Fix a memory leak that occurred on a specific case of using a SP-GiST index
Fix for pg_verify_checksums incorrectly reporting on files that are not expected \
to have checksums
Prevent the PostgreSQL server from starting when wal_level is set to a value \
that cannot support an existing replication slot
Ensure that the server will process already-received NOTIFY and SIGTERM \
interrupts before waiting for client input
Allow PL/Ruby to work with newer versions of PostgreSQL
Fix for character-class checks on Windows for Unicode characters above U+FFFF, \
which affected full-text search as well as contrib/ltree and contrib/pg_trgm
Fix a case where psql would not report the receipt of a message from a NOTIFY \
call until after the next command
Fix build problems on macOS 10.14 (Mojave)
Several build fixes for the Windows platform
This updates also contains tzdata release 2018g for DST law changes in Chile, \
Fiji, Morocco, and Russia (Volgograd), plus historical corrections for China, \
Hawaii, Japan, Macau, and North Korea.

Log message:
postgresql: updated to 10.5, 9.6.10, 9.5.14, 9.4.19, 9.3.24
The PostgreSQL Global Development Group has released an update to all supported \
versions of our database system, including 10.5, 9.6.10, 9.5.14, 9.4.19, 9.3.24. \
This release fixes two security issues as well as bugs reported over the last \
three months.
SECURITY ISSUES:
CVE-2018-10915: CERTAIN HOST CONNECTION PARAMETERS DEFEAT CLIENT-SIDE SECURITY \
DEFENSES
CVE-2018-10925: MEMORY DISCLOSURE AND MISSING AUTHORIZATION IN INSERT ... ON \
CONFLICT DO UPDATE
BUG FIXES AND IMPROVEMENTS
Several fixes related to VACUUM, including an issue that could lead to data \
corruption in certain system catalog tables
Several fixes for replaying write-ahead logs, including a case where a \
just-promoted standby server would not restart if it crashed before its first \
post-recovery checkpoint
Several performance improvements for replaying write-ahead logs
Several fixes for logical replication and logical decoding, including ensuring \
logical WAL senders are reporting the streaming state correctly
Allow replication slots to be dropped in single-user mode
Fix to have variance and similar aggregate functions return accurate results \
when executed using parallel query
Fix SQL-standard FETCH FIRST syntax to allow parameters ($n), as the standard expects
Fix to ensure that a process doing a parallel index scan will respond to \
signals, such as one to abort a query
Fix EXPLAIN's accounting for resource usage, particularly buffer accesses, in \
parallel workers
Several fixes for the query planner including improving the cost estimates for \
hash-joins and choosing to use indexes for mergejoins on composite type columns
Fix performance regression related to POSIX semaphores for multi-CPU systems \
running Linux or FreeBSD
Fix for GIN indexes that could lead to an assertion failure after a pg_upgrade \
from a version before PostgreSQL 9.4
Fix for SHOW ALL to display superuser configuration settings to roles that are \
allowed to read all settings
Fix issue where COPY FROM .. WITH HEADER would drop a line after every \
4,294,967,296 lines processed
Several fixes for XML support, including using the document node as the context \
for XPath queries as defined in the SQL standard, which affects the xpath and \
xpath_exists functions, as well as XMLTABLE
Fix libpq for certain cases where hostaddr is used
Several ecpg fixes for Windows
Fix password prompting in Windows client programs so that echo is properly disabled
Several pg_dump fixes, including correctly outputting REPLICA IDENTITY \
properties for constraint indexes
Make pg_upgrade check that the old server was shut down cleanly