./databases/postgresql17-plpython, PL/Python procedural language for the PostgreSQL backend

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


Branch: CURRENT, Version: 17.5, Package name: postgresql17-plpython-17.5, Maintainer: adam

PL/Python allows you to write functions in the Python programming
language that may be used in SQL queries as if they were built into
Postgres. The PL/Python intepreter is a full Python interpreter.

PL/Python is currently only available as an "untrusted" language
(meaning it does not offer any way of restricting what users can do
in it). It has therefore been named "plpythonu". The trusted variant
plpython may become available again in future, if a new secure execution
mechanism is developed in Python.



Package options: icu, lz4, nls

Master sites:

Filesize: 21089.037 KB

Version history: (Expand)


CVS history: (Expand)


   2025-05-09 15:46:35 by Adam Ciarcinski | Files touched by this commit (64) | Package updated
Log message:
postgresql: updated to 17.5, 16.9, 15.13, 14.18, 13.21

PostgreSQL 17.5, 16.9, 15.13, 14.18, and 13.21

CVE-2025-4207: PostgreSQL GB18030 encoding validation can read one byte past end \ 
of allocation for text that fails validation

Bug Fixes and Improvements

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

Handle self-referential foreign keys on partitioned tables correctly. Creating \ 
or attaching partitions failed to make the required catalog entries for a \ 
foreign-key constraint if the table referenced by the constraint was the same \ 
partitioned table. This resulted in failure to enforce the constraint fully. To \ 
fix this, please see the instructions in the "Updating" section.
Fix for potential data loss issue when using BRIN bloom indexes (e.g. using the \ 
date_bloom_ops operator class).
Fix MERGE into a partitioned table with DO NOTHING actions.
Prevent failure in INSERT commands when the table has a GENERATED column of a \ 
domain type and the domain's constraints disallow NULL values.
Fix ALTER TABLE .. ADD COLUMN to correctly handle the case of a domain type that \ 
has its own default value and the DEFAULT for the column is not set.
Fix issues when performing casts within the keys of JSON constructor expressions.
Fix XMLSERIALIZE() so that the INDENT option is correctly dumped out when it's \ 
present in views or rules. This was noticeable on restores.
Several query planner fixes, including avoiding a premature evaluation of \ 
arguments in an aggregate function that has both FILTER and either ORDER BY or \ 
DISTINCT clauses that could lead to unnecessary failures.
Fix for potentially returning incorrect results when a bitmap scan without \ 
output columns is executed while vacuum is also running on the same table.
Fix performance issues in GIN index search startup when there are many search \ 
keys, for example, jsonbcol ?| array[...] with tens of thousands of array \ 
elements.
Ensure that I/O statistics of active WAL senders are reported within at most one \ 
second.
Fix race condition in handling of synchronous_standby_names immediately after \ 
startup, where a backend might fail to wait for a synchronous commit.
Avoid infinite loop if scram_iterations is set to INT_MAX.
Several fixes for logical replication, including handling of vacuum around \ 
deleted rows that are still required for logical decoding.
Prevent potential data loss when schema modification operations (DDL) that don't \ 
take a strong lock affect tables that are being logically replicated.
Prevent issues in logical replication that could allow duplicate data to be \ 
applied due to apply worker error handling.
Improve how reindexdb handles scheduling parallel reindex operations to achieve \ 
the expected amount of parallelism.

This release also updates time zone data files to tzdata release 2025b for DST \ 
law changes in Chile, plus historical corrections for Iran. Additionally, there \ 
is a new time zone America/Coyhaique for Chile's Aysén Region, to account for \ 
it changing to UTC-03 year-round, which diverges from America/Santiago.
   2025-05-06 14:07:36 by Thomas Klausner | Files touched by this commit (124)
Log message:
*: SOEXT -> SHLIB_EXT
   2025-04-17 23:53:13 by Thomas Klausner | Files touched by this commit (2449)
Log message:
*: recursive bump for icu 77 and libxml2 2.14
   2025-04-02 14:27:43 by Patrick Welche | Files touched by this commit (8)
Log message:
Render postgresql17 CONFLICTS as harmless as those of postgresql16
   2024-11-16 11:13:53 by Adam Ciarcinski | Files touched by this commit (105) | Package updated
Log message:
postgresql: updated to 17.1, 16.5, 15.9, 14.14, 13.17

PostgreSQL 12 is now end-of-life.

Security Issues
* CVE-2024-10976: PostgreSQL row security below e.g. subqueries disregards user \ 
ID changes
* CVE-2024-10977: PostgreSQL libpq retains an error message from man-in-the-middle
* CVE-2024-10978: PostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong \ 
user ID
* CVE-2024-10979: PostgreSQL PL/Perl environment variable changes execute \ 
arbitrary code

Bug Fixes and Improvements

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

Fix when attaching or detaching table partitions with foreign key constraints. \ 
After upgrade, users impacted by this issue will need to perform manual steps to \ 
finish fixing it. Please see the "Upgrading" section and the release \ 
notes for more information.
Fix when using libc as the default collation provider when LC_CTYPE is C while \ 
LC_COLLATE is a different locale. This could lead to incorrect query results. If \ 
you have these settings in your database, please reindex any affected indexes \ 
after updating to this release. This issue impacted 17.0 only.
Several query planner fixes, including disallowing joining partitions \ 
(partitionwise join) if the collations of the partitions don't match.
Fix possible wrong answers or wrong varnullingrels planner errors for MERGE ... \ 
WHEN NOT MATCHED BY SOURCE actions.
Fix validation of the COPY FORCE_NOT_NULL and FORCE_NULL.
Fix server crash when a json_objectagg() call contains a volatile function.
Ensure there's a registered dependency between a partitioned table and a \ 
non-built-in access method specified in CREATE TABLE ... USING. This fix only \ 
prevents problems for partitioned tables created after this update.
Fix race condition in committing a serializable transaction.
Fix race condition in COMMIT PREPARED that could require manual file removal \ 
after a crash-and-recovery.
Fix for pg_cursors view to prevent errors by excluding cursors that aren't \ 
completely set up.
Reduce logical decoding memory consumption.
Fix to prevent stable functions from receiving stale row values when they're \ 
called from a CALL statement's argument list and the CALL is within a PL/pgSQL \ 
EXCEPTION block.
Fix for JIT crashes on ARM (aarch64) systems.
The psql \watch now treats values that are less than 1ms to be 0 (no wait \ 
between executions).
Fix failure to use credentials for a replication user in the password file (pgpass)
pg_combinebackup now throws an error if an incremental backup file is present in \ 
a directory that should contain a full backup.
Fix to avoid reindexing temporary tables and indexes in vacuumdb and parallel \ 
reindexdb
   2024-11-14 23:22:33 by Thomas Klausner | Files touched by this commit (2428)
Log message:
*: recursive bump for icu 76 shlib major version bump
   2024-11-08 14:43:39 by Adam Ciarcinski | Files touched by this commit (42)
Log message:
postgresql17: added version 17.0

PostgreSQL 17 builds on decades of open source development, improving its
performance and scalability while adapting to emergent data access and storage
patterns. This release of PostgreSQL adds significant overall performance
gains, including an overhauled memory management implementation for vacuum,
optimizations to storage access and improvements for high concurrency
workloads, speedups in bulk loading and exports, and query execution
improvements for indexes. PostgreSQL 17 has features that benefit brand new
workloads and critical systems alike, such as additions to the developer
experience with the SQL/JSON JSON_TABLE command, and enhancements to logical
replication that simplify management of high availability workloads and major
version upgrades.