./databases/postgresql11-contrib, Contrib subtree of tools and plug-ins

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 11.9nb1, Package name: postgresql11-contrib-11.9nb1, Maintainer: adam

This subtree contains porting tools, analysis utilities, and plug-in
features that are not part of the core PostgreSQL system, mainly because
they address a limited audience or are too experimental to be part of
the main source tree. This does not preclude their usefulness.


Required to run:
[textproc/libxml2] [security/heimdal] [databases/postgresql11-client] [databases/postgresql11-server]

Required to build:
[pkgtools/cwrappers]

Package options: gssapi, nls

Master sites:

SHA1: aedb423d7f42a46fccf64ff1411fd8f5180f51e7
RMD160: 8a1afd0d5d4e5f3d6e27d30c268dabf66a0db51c
Filesize: 19491.229 KB

Version history: (Expand)


CVS history: (Expand)


   2020-08-31 20:13:29 by Thomas Klausner | Files touched by this commit (3631) | Package updated
Log message:
*: bump PKGREVISION for perl-5.32.
   2020-08-14 08:56:26 by Adam Ciarcinski | Files touched by this commit (59) | Package updated
Log message:
postgresql: updated to 12.4, 11.9, 10.14, 9.6.19, 9.5.23

PostgreSQL 12.4, 11.9, 10.14, 9.6.19, 9.5.23

Security Issues

CVE-2020-14349: Uncontrolled search path element in logical replication.
Versions Affected: 10 - 12.

The PostgreSQL search_path setting determines schemas searched for tables, \ 
functions, operators, etc. The CVE-2018-1058 fix caused most PostgreSQL-provided \ 
client applications to sanitize search_path, but logical replication continued \ 
to leave search_path unchanged. Users of a replication publisher or subscriber \ 
database can create objects in the public schema and harness them to execute \ 
arbitrary SQL functions under the identity running replication, often a \ 
superuser. Installations having adopted a documented secure schema usage pattern \ 
are not vulnerable.

The PostgreSQL project thanks Noah Misch for reporting this problem.

CVE-2020-14350: Uncontrolled search path element in CREATE EXTENSION.
Versions Affected: 9.5 - 12. The security team typically does not test \ 
unsupported versions, but this problem is quite old.

When a superuser runs certain CREATE EXTENSION statements, users may be able to \ 
execute arbitrary SQL functions under the identity of that superuser. The \ 
attacker must have permission to create objects in the new extension's schema or \ 
a schema of a prerequisite extension. Not all extensions are vulnerable.

In addition to correcting the extensions provided with PostgreSQL, the \ 
PostgreSQL Global Development Group is issuing guidance for third-party \ 
extension authors to secure their own work.

Bug Fixes and Improvements

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

Some of these fixes include:

Fix edge cases in partition pruning involving multiple partition key columns \ 
with multiple or no constraining WHERE clauses.
Several fixes for query planning and execution involving partitions.
Fix for determining when to execute a column-specific UPDATE trigger on a \ 
logical replication subscriber.
pg_replication_slot_advance() now updates the oldest xmin and LSN values, as the \ 
failure to do this could prevent resources (e.g. WAL files) from being cleaned \ 
up.
Fix a performance regression in ts_headline().
Ensure that pg_read_file() and related functions read until EOF is reached, \ 
which fixes compatibility with pipes and other virtual files.
Forbid numeric NaN values in jsonpath computations, which do not exist in SQL \ 
nor JSON.
Several fixes for NaN inputs with aggregate functions. This fixes a change in \ 
PostgreSQL 12 where NaN values caused the following aggregates to emit values of \ 
0 instead of NaN: corr(), covar_pop(), regr_intercept(), regr_r2(), \ 
regr_slope(), regr_sxx(), regr_sxy(), regr_syy(), stddev_pop(), and var_pop().
time and timetz values fractionally greater than 24:00:00 are now rejected.
Several fixes for EXPLAIN, including a fix for reporting resource usage when a \ 
plan uses parallel workers with "Gather Merge" nodes.
Fix timing of constraint revalidation in ALTER TABLE that could lead to odd errors.
Fix for REINDEX CONCURRENTLY that could prevent old values from being included \ 
in future logical decoding output.
Fix for LATERAL references that could potentially cause crashes during query \ 
execution.
Use the collation specified for a query when estimating operator costs
Fix conflict-checking anomalies in SERIALIZABLE transaction isolation mode.
Ensure checkpointer process discards file sync requests when fsync is off
Fix issue where pg_control could be written out with an inconsistent checksum, \ 
which could lead to the inability to restart the database if it crashed before \ 
the next pg_control update.
Ensure that libpq continues to try to read from the database connection socket \ 
after a write failure, as this allows the connection to collect any final error \ 
messages from the server.
Report out-of-disk-space errors properly in pg_dump and pg_basebackup
Several fixes for pg_restore, including a fix for parallel restore on tables \ 
that have both table-level and column-level privileges.
Fix for pg_upgrade to ensure it runs with vacuum_defer_cleanup_age set to 0.
Fix how pg_rewind handles just-deleted files in the source data directory
Fix failure to initialize local state correctly in contrib/dblink, which could \ 
lead to dblink_close() issuing an unexpected COMMIT on the remote server.
Change contrib/amcheck to not report about deleted index pages that are empty, \ 
as this is normal during WAL replay.
   2020-06-02 10:25:05 by Adam Ciarcinski | Files touched by this commit (1689)
Log message:
Revbump for icu
   2020-05-12 17:53:19 by Roland Illig | Files touched by this commit (16)
Log message:
databases/postgresql*: suppress USE_TOOLS+=perl warning
   2020-02-14 18:06:46 by Adam Ciarcinski | Files touched by this commit (67) | Package updated
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.
   2020-01-18 22:51:16 by Jonathan Perkin | Files touched by this commit (1836)
Log message:
*: Recursive revision bump for openssl 1.1.1.
   2019-11-02 16:38:12 by Roland Illig | Files touched by this commit (115)
Log message:
databases: align variable assignments

pkglint -Wall -F --only aligned -r

No manual corrections.
   2018-11-09 19:12:28 by Adam Ciarcinski | Files touched by this commit (63) | Package updated
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.