./databases/postgresql14-plperl, PL/Perl procedural language for the PostgreSQL backend

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


Branch: CURRENT, Version: 14.3, Package name: postgresql14-plperl-14.3, Maintainer: adam

PL/Perl allows you to write functions in the Perl programming language
that may be used in SQL queries as if they were built into Postgres.
The PL/Perl intepreter is a full Perl interpreter. However, certain
operations have been disabled in order to maintain the security of the
system.



Package options: gssapi, lz4, nls

Master sites:

Filesize: 21574.404 KB

Version history: (Expand)


CVS history: (Expand)


   2022-05-12 21:02:47 by Adam Ciarcinski | Files touched by this commit (55) | Package updated
Log message:
postgresqlNN: updated to 14.3, 13.7, 12.11, 11.16, and 10.21

The PostgreSQL Global Development Group has released an update to all supported \ 
versions of PostgreSQL, including 14.3, 13.7, 12.11, 11.16, and 10.21. This \ 
release closes one security vulnerability and fixes over 50 bugs reported over \ 
the last three months.

CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted \ 
operation" sandbox.

Versions Affected: 10 - 14. The security team typically does not test \ 
unsupported versions, but this problem is quite old.

Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and \ 
pg_amcheck made incomplete efforts to operate safely when a privileged user is \ 
maintaining another user's objects. Those commands activated relevant \ 
protections too late or not at all. An attacker having permission to create \ 
non-temp objects in at least one schema could execute arbitrary SQL functions \ 
under a superuser identity.

While promptly updating PostgreSQL is the best remediation for most users, a \ 
user unable to do that can work around the vulnerability by disabling \ 
autovacuum, not manually running the above commands, and not restoring from \ 
output of the pg_dump command. Performance may degrade quickly under this \ 
workaround. VACUUM is safe, and all commands are fine when a trusted user owns \ 
the target object.

Bug Fixes and Improvements

This update fixes over 50 bugs that were reported in the last several months. \ 
The issues listed below affect PostgreSQL 14. Some of these issues may also \ 
affect other supported versions of PostgreSQL.

Included in this release:

Fix issue that could lead to corruption of GiST indexes on ltree columns. After \ 
upgrading, you will need to reindex any GiST indexes on ltree columns.
Column names in tuples produced by a whole-row variable (e.g. tbl.*) outside of \ 
a top-level of a SELECT list are now always associated with those of the \ 
associated named composite type, if there is one. The release notes detail a \ 
workaround if you depend on the previous behavior.
Fix incorrect rounding when extracting epoch values from interval types.
Prevent issues with calling pg_stat_get_replication_slot(NULL).
Fix incorrect output for types timestamptz and timetz in table_to_xmlschema().
Fix errors related to a planner issue that affected asynchronous remote queries.
Fix planner failure if a query using SEARCH or CYCLE features contains a \ 
duplicate common-table expression (WITH) name.
Fix ALTER FUNCTION to support changing a function's parallelism property and its \ 
SET-variable list in the same command.
Fix incorrect sorting of table rows when using CLUSTER on an index whose leading \ 
key is an expression.
Prevent data loss if a system crash occurs shortly after a sorted GiST index build.
Fix risk of deadlock failures while dropping a partitioned index.
Fix race condition between DROP TABLESPACE and checkpointing that could fail to \ 
remove all dead files from the tablespace directory.
Fix potential issue in crash recovery after a TRUNCATE command that overlaps \ 
with a checkpoint.
Re-allow _ as the first character in a custom configuration parameter name.
Fix PANIC: xlog flush request is not satisfied failure during standby promotion \ 
when there is a missing WAL continuation record.
Fix possibility of self-deadlock in hot standby conflict handling.
Ensure that logical replication apply workers can be restarted when the server \ 
is near the max_sync_workers_per_subscription limit.
Disallow execution of SPI functions during PL/Perl function compilation.
libpq now accepts root-owned SSL private key files, which matches the rules the \ 
server has used since the 9.6 release.
Re-allow database.schema.table patterns in psql, pg_dump, and pg_amcheck.
Several fixes for pageinspect to improve overall stability.
Disable batch insertion in postgres_fdw when BEFORE INSERT ... FOR EACH ROW \ 
triggers exist on the foreign table.
Update JIT code to work with LLVM 14.
   2022-05-12 15:03:58 by David Brownlee | Files touched by this commit (9)
Log message:
Add lz4 to postgresql14 options (enabled by default)

Bump PKGREVISION on all including packages just to be on the safe side
   2022-04-18 21:12:27 by Adam Ciarcinski | Files touched by this commit (1798) | Package updated
Log message:
revbump for textproc/icu update
   2022-02-11 09:31:25 by Adam Ciarcinski | Files touched by this commit (56) | Package updated
Log message:
postgresql1N: updated to 14.2, 13.6, 12.10, 11.15, and 10.20

PostgreSQL 14.2, 13.6, 12.10, 11.15, and 10.20 Released!

This update fixes over 55 bugs that were reported in the last several months. \ 
The issues listed below affect PostgreSQL 14. Some of these issues may also \ 
affect other supported versions of PostgreSQL.

Included in this release:

Fix for a low probability scenario of index corruption when a HOT (heap-only \ 
tuple) chain changes state during VACUUM. Encountering this issue is unlikely, \ 
but if you are concerned, please consider reindexing.
Fix for using REINDEX CONCURRENTLY on TOAST table indexes to prevent corruption. \ 
You can fix any TOAST indexes by reindexing them again.
The psql \password command now defaults to setting the password for the role \ 
defined by CURRENT_USER. Additionally, the role name is now included in the \ 
password prompt.
Build extended statistics for partitioned tables. If you previously added \ 
extended statistics to a partitioned table, you should run ANALYZE on those \ 
tables. As autovacuum currently does not process partitioned tables, you must \ 
periodically run ANALYZE on any partitioned tables to update their statistics.
Fix crash with ALTER STATISTICS when the statistics object is dropped concurrently.
Fix crash with multiranges when extracting variable-length data types.
Several fixes to the query planner that lead to incorrect query results.
Several fixes for query plan memoization.
Fix startup of a physical replica to tolerate transaction ID wraparound.
When using logical replication, avoid duplicate transmission of a partitioned \ 
table's data when the publication includes both the child and parent tables.
Disallow altering data type of a partitioned table's columns when the \ 
partitioned table's row type is used as a composite type elsewhere.
Disallow ALTER TABLE ... DROP NOT NULL for a column that is part of a replica \ 
identity index.
Several fixes for caching that correct logical replication behavior and improve \ 
performance.
Fix memory leak when updating expression indexes.
Avoid leaking memory during REASSIGN OWNED BY operations that reassign ownership \ 
of many objects.
Fix display of whole-row variables appearing in INSERT ... VALUES rules.
Fix race condition that could lead to failure to localize error messages that \ 
are reported early in multi-threaded use of libpq or ecpglib.
Fix psql \d command for identifying parent triggers.
Fix failures on Windows when using the terminal as data source or destination. \ 
This affected the psql \copy command and using pg_recvlogical with -f -.
Fix the pg_dump --inserts and --column-inserts modes to handle tables that \ 
contain both generated and dropped columns.
Fix edge cases in how postgres_fdw handles asynchronous queries. These errors \ 
could lead to crashes or incorrect results when attempting to run parallel scans \ 
of foreign tables.
For the full list of changes available, please review the release notes.
   2021-12-08 17:07:18 by Adam Ciarcinski | Files touched by this commit (3063)
Log message:
revbump for icu and libffi
   2021-11-16 11:14:39 by Adam Ciarcinski | Files touched by this commit (27) | Package updated
Log message:
postgresql: updated to 14.1, 13.5, 12.9, 11.14, 10.19, 9.6.24

PostgreSQL 14.1, 13.5, 12.9, 11.14, 10.19, and 9.6.24

Security Issues

CVE-2021-23214: Server processes unencrypted bytes from man-in-the-middle

Versions Affected: 9.6 - 14. The security team typically does not test \ 
unsupported versions, but this problem is quite old.

When the server is configured to use trust authentication with a clientcert \ 
requirement or to use cert authentication, a man-in-the-middle attacker can \ 
inject arbitrary SQL queries when a connection is first established, despite the \ 
use of SSL certificate verification and encryption.

The PostgreSQL project thanks Jacob Champion for reporting this problem.

CVE-2021-23222: libpq processes unencrypted bytes from man-in-the-middle

Versions Affected: 9.6 - 14. The security team typically does not test \ 
unsupported versions, but this problem is quite old.

A man-in-the-middle attacker can inject false responses to the client's first \ 
few queries, despite the use of SSL certificate verification and encryption.

If more preconditions hold, the attacker can exfiltrate the client's password or \ 
other confidential data that might be transmitted early in a session. The \ 
attacker must have a way to trick the client's intended server into making the \ 
confidential data accessible to the attacker. A known implementation having that \ 
property is a PostgreSQL configuration vulnerable to CVE-2021-23214.

As with any exploitation of CVE-2021-23214, the server must be using trust \ 
authentication with a clientcert requirement or using cert authentication. To \ 
disclose a password, the client must be in possession of a password, which is \ 
atypical when using an authentication configuration vulnerable to \ 
CVE-2021-23214. The attacker must have some other way to access the server to \ 
retrieve the exfiltrated data (a valid, unprivileged login account would be \ 
sufficient).

The PostgreSQL project thanks Jacob Champion for reporting this problem.

Bug Fixes and Improvements

This update fixes over 40 bugs that were reported in the last several months. \ 
The issues listed below affect PostgreSQL 14. Some of these issues may also \ 
affect other supported versions of PostgreSQL.

Some of these fixes include:

Fix physical replication for cases where the primary crashes after shipping a \ 
WAL segment that ends with a partial WAL record. When applying this update, \ 
update your standby servers before the primary so that they will be ready to \ 
handle the fix if the primary happens to crash.
Fix parallel VACUUM so that it will process indexes below the \ 
min_parallel_index_scan_size threshold if the table has at least two indexes \ 
that are above that size. This problem does not affect autovacuum. If you are \ 
affected by this issue, you should reindex any manually-vacuumed tables.
Fix causes of CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY writing corrupt \ 
indexes. You should reindex any concurrently-built indexes.
Fix for attaching/detaching a partition that could allow certain INSERT/UPDATE \ 
queries to misbehave in active sessions.
Fix for creating a new range type with CREATE TYPE that could cause problems for \ 
later event triggers or subsequent executions of the CREATE TYPE command.
Fix updates of element fields in arrays of a domain that is a part of a composite.
Disallow the combination of FETCH FIRST WITH TIES and FOR UPDATE SKIP LOCKED.
Fix corner-case loss of precision in the numeric power() function.
Fix restoration of a Portal's snapshot inside a subtransaction, which could lead \ 
to a crash. For example, this could occur in PL/pgSQL when a COMMIT is \ 
immediately followed by a BEGIN ... EXCEPTION block that performs a query.
Clean up correctly if a transaction fails after exporting its snapshot. This \ 
could occur if a replication slot was created then rolled back, and then another \ 
replication slot was created in the same session.
Fix for "overflowed-subtransaction" wraparound tracking on standby \ 
servers that could lead to performance degradation.
Ensure that prepared transactions are properly accounted for during promotion of \ 
a standby server.
Ensure that the correct lock level is used when renaming a table.
Avoid crash when dropping a role that owns objects being dropped concurrently.
Disallow setting huge_pages to on when shared_memory_type is sysv
Fix query type checking in the PL/pgSQL RETURN QUERY.
Several fixes for pg_dump, including the ability to dump non-global default \ 
privileges correctly.
Use the CLDR project's data to map Windows time zone names to IANA time zones.
This update also contains tzdata release 2021e for DST law changes in Fiji, \ 
Jordan, Palestine, and Samoa, plus historical corrections for Barbados, Cook \ 
Islands, Guyana, Niue, Portugal, and Tonga.

Also, the Pacific/Enderbury zone has been renamed to Pacific/Kanton. Also, the \ 
following zones have been merged into nearby, more-populous zones whose clocks \ 
have agreed with them since 1970: Africa/Accra, America/Atikokan, \ 
America/Blanc-Sablon, America/Creston, America/Curacao, America/Nassau, \ 
America/Port_of_Spain, Antarctica/DumontDUrville, and Antarctica/Syowa. In all \ 
these cases, the previous zone name remains as an alias.
   2021-10-08 12:23:45 by Adam Ciarcinski | Files touched by this commit (44) | Package updated
Log message:
postgresql14: added version 14.0

PostgreSQL 14 contains many new features and enhancements, including:

Stored procedures can now return data via OUT parameters.

The SQL-standard SEARCH and CYCLE options for common table expressions have been \ 
implemented.

Subscripting can now be applied to any data type for which it is a useful \ 
notation, not only arrays. In this release, the jsonb and hstore types have \ 
gained subscripting operators.

Range types have been extended by adding multiranges, allowing representation of \ 
noncontiguous data ranges.

Numerous performance improvements have been made for parallel queries, \ 
heavily-concurrent workloads, partitioned tables, logical replication, and \ 
vacuuming.

B-tree index updates are managed more efficiently, reducing index bloat.

VACUUM automatically becomes more aggressive, and skips inessential cleanup, if \ 
the database starts to approach a transaction ID wraparound condition.

Extended statistics can now be collected on expressions, allowing better \ 
planning results for complex queries.

libpq now has the ability to pipeline multiple queries, which can boost \ 
throughput over high-latency connections.