Log message:
Retired mysql55 and postgresql94 packages

Log message:
databases/postgresql: suppress USE_TOOLS+=perl warning

Log message:
postgresqlNN: updated to 12.2, 11.7, 10.12, 9.6.17, 9.5.21, and 9.4.26

PostgreSQL 12.2, 11.7, 10.12, 9.6.17, 9.5.21, and 9.4.26

PostgreSQL 9.4 Now EOL

This is the last release for PostgreSQL 9.4, which will no longer receive \ 
security updates and bug fixes. PostgreSQL 9.4 introduced new features such as \ 
JSONB support, the ALTER SYSTEM command, the ability to stream logical changes \ 
to an output plugin, and more.

While we are very proud of this release, these features are also found in newer \ 
versions of PostgreSQL. Many of these features have also received improvements, \ 
and, per our versioning policy, it is time to retire PostgreSQL 9.4.

To receive continued support, we suggest that you make plans to upgrade to a \ 
newer, supported version of PostgreSQL. Please see the PostgreSQL versioning \ 
policy for more information.

Security Issues

CVE-2020-1720: ALTER ... DEPENDS ON EXTENSION is missing authorization checks.
Versions Affected: 9.6 - 12

The ALTER ... DEPENDS ON EXTENSION sub-commands do not perform authorization \ 
checks, which can allow an unprivileged user to drop any function, procedure, \ 
materialized view, index, or trigger under certain conditions. This attack is \ 
possible if an administrator has installed an extension and an unprivileged user \ 
can CREATE, or an extension owner either executes DROP EXTENSION predictably or \ 
can be convinced to execute DROP EXTENSION.

Bug Fixes and Improvements

This update also fixes over 75 bugs that were reported in the last several \ 
months. Some of these issues affect only version 12, but may also affect all \ 
supported versions.

Some of these fixes include:

Fix for partitioned tables with foreign-key references where TRUNCATE ... \ 
CASCADE would not remove all data. If you have previously used TRUNCATE ... \ 
CASCADE on a partitioned table with foreign-key references please see the \ 
"Updating" section for verification and cleanup steps.
Fix failure to add foreign key constraints to table with sub-partitions (aka a \ 
multi-level partitioned table). If you have previously used this functionality, \ 
you can fix it by either detaching and re-attaching the affected partition, or \ 
by dropping and re-adding the foreign key constraint to the parent table. You \ 
can find more information on how to perform these steps in the ALTER TABLE \ 
documentation.
Fix performance issue for partitioned tables introduced by the fix for \ 
CVE-2017-7484 that now allows the planner to use statistics on a child table for \ 
a column that the user is granted access to on the parent table when the query \ 
contains a leaky operator.
Several other fixes and changes for partitioned tables, including disallowing \ 
partition key expressions that return pseudo-types, such as RECORD.
Fix for logical replication subscribers for executing per-column UPDATE triggers.
Fix for several crashes and failures for logical replication subscribers and \ 
publishers.
Improve efficiency of logical replication with REPLICA IDENTITY FULL.
Ensure that calling pg_replication_slot_advance() on a physical replication slot \ 
will persist changes across restarts.
Several fixes for the walsender processes.
Improve performance of hash joins with very large inner relations.
Fix placement of "Subplans Removed" field in EXPLAIN output by placing \ 
it with its parent Append or MergeAppend plan.
Several fixes for parallel query plans.
Several fixes for query planner errors, including one that affected joins to \ 
single-row subqueries.
Several fixes for MCV extend statistics, including one for incorrect estimation \ 
for OR clauses.
Improve efficiency of parallel hash join on CPUs with many cores.
Ignore the CONCURRENTLY option when performing an index creation, drop, or \ 
reindex on a temporary table.
Fall back to non-parallel index builds when a parallelized CREATE INDEX has no \ 
free dynamic shared memory slots.
Several fixes for GiST & GIN indexes.
Fix possible crash in BRIN index operations with box, range and inet data types.
Fix support for BRIN hypothetical indexes.
Fix failure in ALTER TABLE when a column referenced in a GENERATED expression is \ 
added or changed in type earlier in the same ALTER TABLE statement.
Fix handling of multiple AFTER ROW triggers on a foreign table.
Fix off-by-one result for EXTRACT(ISOYEAR FROM timestamp) for BC dates.
Prevent unwanted lowercasing and truncation of RADIUS authentication parameters \ 
in the pg_hba.conf file.
Several fixes for GSSAPI support, including having libpq accept all GSS-related \ 
connection parameters even if the GSSAPI code is not compiled in.
Several fixes for pg_dump and pg_restore when run in parallel mode.
Fix crash with postgres_fdw when trying to execute a remote query on the remote \ 
server such as UPDATE remote_tab SET (x,y) = (SELECT ...).
Disallow NULL category values in the crosstab() function of contrib/tablefunc to \ 
prevent crashes.
Several fixes for Windows, including a race condition that could cause timing \ 
oddities with NOTIFY.
Several ecpg fixes.

Log message:
*: Recursive revision bump for openssl 1.1.1.

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.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

Log message:
postgresqlNN: updated to 10.3, 9.6.8, 9.5.12, 9.4.17, 9.3.22

PostgreSQL 10.3, 9.6.8, 9.5.12, 9.4.17, and 9.3.22:
The purpose of this release is to address CVE-2018-1058, which describes how a \ 
user can create like-named objects in different schemas that can change the \ 
behavior of other users' queries and cause unexpected or malicious behavior, \ 
also known as a "trojan-horse" attack. Most of this release centers \ 
around added documentation that describes the issue and how to take steps to \ 
mitigate the impact on PostgreSQL databases.

Log message:
postgresql: updated to the latest

The PostgreSQL Global Development Group has released an update to all supported \ 
versions of our database system, including 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, \ 
and 9.2.24. This release fixes three security issues. This release also fixes \ 
issues found in BRIN indexing, logical replication and other bugs reported over \ 
the past three months.

All users using the affected versions of PostgreSQL should update as soon as \ 
possible. If you use BRIN indexes or contrib/start-scripts, please see the \ 
release notes for additional post-upgrade steps.

Security Issues

Three security vulnerabilities have been fixed by this release:

CVE-2017-12172: Start scripts permit database administrator to modify root-owned \ 
files
CVE-2017-15098: Memory disclosure in JSON functions
CVE-2017-15099: INSERT ... ON CONFLICT DO UPDATE fails to enforce SELECT privileges

Bug Fixes and Improvements

This update also fixes a number of bugs reported in the last few months. Some of \ 
these issues affect only version 10, but many affect all supported versions:

Fix a race condition in BRIN indexing that could cause some rows to not be \ 
included in the indexing.
Fix crash when logical decoding is invoked from a PL language function.
Several fixes for logical replication.
Restored behavior for CTEs attached to INSERT/UPDATE/DELETE statements to \ 
pre-version 10.
Prevent low-probability crash in processing of nested trigger firings.
Do not evaluate an aggregate function's argument expressions when the conditions \ 
in the FILTER clause evaluate to FALSE. This complies with SQL-standard \ 
behavior.
Fix incorrect query results when multiple GROUPING SETS columns contain the same \ 
simple variable.
Fix memory leak over the lifespan of a query when evaluating a set-returning \ 
function from the target list in a SELECT.
Several fixes for parallel query execution, including fixing a crash in the \ 
parallel execution of certain queries that contain a certain type of bitmap \ 
scan.
Fix json_build_array(), json_build_object(), jsonb_build_array(), and \ 
jsonb_build_object() to handle explicit VARIADIC arguments correctly.
Prevent infinite float values from being casted to the numeric type.
Fix autovacuum's “work item” logic to prevent possible crashes and silent \ 
loss of work items.
Several fixes for VIEWs around adding columns to the end of a view.
Fix for hashability detection of range data types that are created by a user.
Improvements on using extended statistics on columns for the purposes of query \ 
planning.
Prevent idle_in_transaction_session_timeout from being ignored when a \ 
statement_timeout occurred earlier.
Fix low-probability loss of NOTIFY messages due more than 2 billion transactions \ 
processing before any queries are executed in the session.
Several file system interaction fixes.
Correctly restore the umask setting when file creation fails in COPY or lo_export().
Fix pg_dump to ensure that it emits GRANT commands in a valid order.
Fix pg_basebackup's matching of tablespace paths to canonicalize both paths \ 
before comparing to help improve Windows compatibility.
Fix libpq to not require user's home directory to exist when trying to read the \ 
"~/.pgpass" file.
Several fixes for ecpg.

Log message:
Make sure the --as-needed linker arg does not leak into the pgxs Makefiles
on Darwin and SunOS where it's not supported. Bump PKGREVISION on *-client.