./databases/postgresql11-client, PostgreSQL database client programs

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


Branch: CURRENT, Version: 11.8nb1, Package name: postgresql11-client-11.8nb1, Maintainer: adam

PostgreSQL is a robust, next-generation, Object-Relational DBMS (ORDBMS),
derived from the Berkeley Postgres database management system. While
PostgreSQL retains the powerful object-relational data model, rich data types
and easy extensibility of Postgres, it replaces the PostQuel query language
with an extended subset of SQL.

PostgreSQL is free and the complete source is available.

This package contains the database client programs.


Required to run:
[textproc/libxml2] [security/heimdal] [security/openssl]

Required to build:
[pkgtools/cwrappers]

Package options: gssapi, nls

Master sites:

SHA1: 82f2b0f6daa5f0ce54127676b8dc5f7fb2680e50
RMD160: fc279ef554a50b79341454f9c538278d3aa13f0e
Filesize: 19455.83 KB

Version history: (Expand)


CVS history: (Expand)


   2020-06-02 10:25:05 by Adam Ciarcinski | Files touched by this commit (1689)
Log message:
Revbump for icu
   2020-05-13 06:58:23 by Roland Illig | Files touched by this commit (12)
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-19 19:42:41 by Amitai Schleier | Files touched by this commit (1)
Log message:
Add missing PLIST entry for nls (cs/pg_verify_checksums-11.mo).
   2019-10-25 06:39:19 by =?UTF-8?B?RnLDqWTDqXJpYyBGYXViZXJ0ZWF1?= | Files touched by this commit (9)
Log message:
postgresql11: make nls support optional
   2019-06-25 18:39:00 by Adam Ciarcinski | Files touched by this commit (1)
Log message:
postgresql11-client: PLIST correction
   2019-05-13 22:38:13 by Adam Ciarcinski | Files touched by this commit (24) | Package updated
Log message:
postgresqlNN: updated to the latest

PostgreSQL 11.3, 10.8, 9.6.13, 9.5.17, and 9.4.22 Released!
The PostgreSQL Global Development Group has released an update to all supported \ 
versions of our database system, including 11.3, 10.8, 9.6.13, 9.5.17, and \ 
9.4.22. This release fixes two security issues in the PostgreSQL server, a \ 
security issue found in two of the PostgreSQL Windows installers, and over 60 \ 
bugs reported over the last three months.

Security Issues

Four security vulnerabilities have been closed by this release:

CVE-2019-10127: BigSQL Windows installer does not clear permissive ACL entries
CVE-2019-10128: EnterpriseDB Windows installer does not clear permissive ACL entries
Due to both the EnterpriseDB and BigSQL Windows installers not locking down the \ 
permissions of the PostgreSQL binary installation directory and the data \ 
directory, an unprivileged Windows user account and an unprivileged PostgreSQL \ 
account could cause the PostgreSQL service account to execute arbitrary code.

This vulnerability is present in all supported versions of PostgreSQL for these \ 
installers, and possibly exists in older versions. Both sets of installers have \ 
fixed the permissions for these directories for both new and existing \ 
installations. If you have installed PostgreSQL on Windows using other methods, \ 
we advise that you check that your PostgreSQL binary directories are writable \ 
only to trusted users and that your data directories are only accessible to \ 
trusted users.

The PostgreSQL project thanks Conner Jones for reporting this problem.

CVE-2019-10129: Memory disclosure in partition routing
Prior to this release, a user running PostgreSQL 11 can read arbitrary bytes of \ 
server memory by executing a purpose-crafted INSERT statement to a partitioned \ 
table.

CVE-2019-10130: Selectivity estimators bypass row security policies
PostgreSQL maintains statistics for tables by sampling data available in \ 
columns; this data is consulted during the query planning process. Prior to this \ 
release, a user able to execute SQL queries with permissions to read a given \ 
column could craft a leaky operator that could read whatever data had been \ 
sampled from that column. If this happened to include values from rows that the \ 
user is forbidden to see by a row security policy, the user could effectively \ 
bypass the policy. This is fixed by only allowing a non-leakproof operator to \ 
use this data if there are no relevant row security policies for the table.

This issue is present in PostgreSQL 9.5, 9.6, 10, and 11. The PostgreSQL project \ 
thanks Dean Rasheed for reporting this problem.

Bug Fixes and Improvements

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

Some of these fixes include:

Several catalog corruption fixes, including one related to running ALTER TABLE \ 
on a partitioned table
Several fixes for partitioning
Avoid server crash when an error occurs while trying to persist a cursor query \ 
across a transaction commit
Avoid O(N^2) performance issue when rolling back a transaction that created many \ 
tables
Fix possible “could not access status of transaction” failures in txid_status()
Fix updatable views to handle explicit DEFAULT items in INSERT .. VALUES \ 
statements where there are multiple VALUES rows
Fix CREATE VIEW to allow zero-column views
Add missing support for the CREATE TABLE IF NOT EXISTS .. AS EXECUTE .. statement
Ensure that sub-SELECTs appearing in row-level-security policy expressions are \ 
executed with the correct user's permissions
Accept XML documents as valid values of type xml when xmloption is set to \ 
content, as required by SQL:2006 and later
Fix incompatibility of GIN-index WAL records that were introduced in 11.2, 10.7, \ 
9.6.12, 9.5.16, and 9.4.21 that affected replica servers running these versions \ 
reading in changes to GIN indexes from primary servers of older versions
Several memory leak fixes as well as fixes to management of dynamic shared memory
Relax panics on fsync and sync_file_range failures for certain cases where a \ 
failure indicated "operation not supported"
Several fixes to the query planner, several of which should lead to planning \ 
improvements
Fix race condition in which a hot-standby postmaster could fail to shut down \ 
after receiving a smart-shutdown request
Several fixes for SCRAM authentication
Fix handling of lc_time settings that imply an encoding different from the \ 
database's encoding
Create the current_logfiles file with the same permissions as other files in the \ 
server's data directory
Several ecpg fixes
Make pg_verify_checksums verify that the data directory it's pointed at is of \ 
the right PostgreSQL version
Several fixes for contrib/postgres_fdw, including one for remote partitions \ 
where an UPDATE could lead to incorrect results or a crash
Several Windows fixes
This update also contains tzdata release 2019a for DST law changes in Palestine \ 
and Metlakatla, plus historical corrections for Israel. Etc/UCT is now a \ 
backward-compatibility link to Etc/UTC, instead of being a separate zone that \ 
generates the abbreviation UCT, which nowadays is typically a typo. PostgreSQL \ 
will still accept UCT as an input zone abbreviation, but it won't output it.