Log message:
Retire postgresql93

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:
Recursive bump for perl5-5.28.0

Log message:
postgresql: updated to 10.2, 9.6.7, 9.5.11, 9.4.16, and 9.3.21

This release fixes two security issues. This release also fixes issues with \ 
VACUUM, GIN indexes, and hash indexes that could lead to data corruption, as \ 
well as fixes for using parallel queries and logical replication.

Security Issues
* CVE-2018-1052: Fix the processing of partition keys containing multiple expressions
* CVE-2018-1053: Ensure that all temporary files made with \ 
"pg_upgrade" are non-world-readable

Bug Fixes and Improvements
* Fix crash and potential disclosure of backend memory when processing partition \ 
keys containing multiple expressions
* Fix potential disclosure of temporary files containing database passwords \ 
created by pg_upgrade by not allowing these files to be world-accessible
* Fix cases where VACUUM would not remove dead rows if they were updated while \ 
"key-share" locked, leading to potential data corruption
* Fix for GIN indexes to prevent bloat by ensuring the pending-insertions list \ 
is cleaned up by VACUUM
* Fix potential index corruption with hash indexes due to failure to mark \ 
metapages as dirty
* Fix several potential crash scenarios for parallel queries, including when a \ 
bitmap heap scan cannot allocate memory
* Fix several potential hang-ups in parallel queries, including when a parallel \ 
worker fails to start
* Fix collection of EXPLAIN statistics from parallel workers
* Prevent fake deadlock failures when multiple sessions are running CREATE INDEX \ 
CONCURRENTLY
* Fix for trigger behavior when using logical replication
* Several fixes for "walsender" functionality to improve stability as \ 
well as visibility into the replication process
* Fix logical decoding to correctly clean up disk files for crashed transactions
* Several fixes for identity columns, including disallowing identity columns on \ 
tables derived from composite types and partitions
* Fix handling of list partitioning constraints for partition keys of boolean \ 
and array types
* Fix incorrectly generated plans for UPDATE and DELETE queries when a table has \ 
a mix of inherited regular and foreign child tables
* Fix incorrect query results from cases involving GROUPING SETS when used with \ 
flattened subqueries
* Fix UNION/INTERSECT/EXCEPT over zero columns, e.g. "SELECT UNION SELECT;"
* Several fixes for subqueries within a LATERAL subquery
* Several improvements for query planning estimation
* Allow a client that supports SCRAM channel binding, such as a future version \ 
of PostgreSQL or libpq, to connect to a PostgreSQL 10 server
* Fix sample INSTR() functions used to help transition from Oracle(r) PL/SQL to \ 
PostgreSQL PL/pgSQL to correctly match Oracle functional behavior
* Fix pg_dump to make permissions (ACL), security label, and comment entries \ 
reliably identifiable in archive outputs
* Modify behavior for contrib/cube's "cube ~> int" operator to make \ 
it compatible with KNN search. This is a backwards incompatible change and any \ 
expression indexes or materialized views using this operator will need to be \ 
reindexed and refreshed, respectively.
* Several fixes in contrib/postgres_fdw to prevent query planner errors
* Added modern examples of auto-start scripts for PostgreSQL on macOS in the \ 
contrib/start-scripts/macos directory
* Several fixes for Windows, including postmaster startup and compatibility with \ 
libperl
* Spinlock fixes and support for Motorola 68K and 88K architectures

Log message:
Bump PKGREVISION of postgresql92 and postgresql93 packages (all to 1)
for the PR 52787 options adjustment, as a precaution.

Log message:
The PostgreSQL Global Development Group has released an update to all supported \ 
versions of our database system, including 9.5.2, 9.4.7, 9.3.12, 9.2.16, and \ 
9.1.21. This release fixes two security issues and one index corruption issue in \ 
version 9.5. It also contains a variety of bug fixes for earlier versions. Users \ 
of PostgreSQL 9.5.0 or 9.5.1 should update as soon as possible.

This release closes security hole CVE-2016-2193, where a query plan might get \ 
reused for more than one ROLE in the same session. This could cause the wrong \ 
set of Row Level Security (RLS) policies to be used for the query.

The update also fixes CVE-2016-3065, a server crash bug triggered by using \ 
pageinspect with BRIN index pages. Since an attacker might be able to expose a \ 
few bytes of server memory, this crash is being treated as a security issue.

Log message:
Bump PKGREVISION for security/openssl ABI bump.

Log message:
Changes:
This update fixes CVE-2014-0060, in which PostgreSQL did not properly enforce \ 
the WITH ADMIN OPTION permission for ROLE management.
This update also fixes some issues which affect binary replication and row \ 
locking, and can cause recoverable data corruption in some cases.
In addition to the above, the following issues are fixed in this release:

Fix WAL logging of visibility map change
Make sure that GIN indexes log all insertions
Get pause_at_recovery_target to pause at correct time
Ensure walreceiver sends hot-standby feedback messages on time
Prevent timeout interrupts from taking control away from mainline code
Eliminate several race conditions
Fix some broken HINTs in error messages
Prevent server lockup on SSL connection loss
Fix two Unicode handling issues
Prevent crash on certain subselect syntax
Prevent crash on select from zero column table
Fix two bugs with LATERAL
Fix issue with UNION ALL, partitioning, and updates
Ensure that ANALYZE understands domains over ranges
Eliminate permissions check when using default tablespace
Fix memory leakage in JSON functions
Allow extensions with event triggers
Distinguish numbers correctly in JSON output
Fix permissions for pg_start_backup() and pg_stop_backup()
Accept SHIFT_JIS as locale name
Fix .* expansion for SQL function variables
Prevent infinite loop on some COPY connection failures
Several fixes for client issues on Windows
Enable building PostgreSQL with Visual Studio 2013
Update time zone files for recent changes

Log message:
Recursive PKGREVISION bump for OpenSSL API version bump.

Log message:
Revbump after updating tcl/tk.