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

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


Branch: CURRENT, Version: 9.4.20, Package name: postgresql94-plpython-9.4.20, 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.


Required to run:
[textproc/libxml2] [lang/python27] [databases/postgresql94-server] [databases/postgresql94-client]

Required to build:
[pkgtools/cwrappers]

Package options: gssapi

Master sites:

SHA1: 9a08fef43a014958c9494214cedff29e20df1d99
RMD160: b897243d3049b5a4aafba1de10e7fdc1a5d3117b
Filesize: 17486.018 KB

Version history: (Expand)


CVS history: (Expand)


   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.
   2018-08-22 11:48:07 by Thomas Klausner | Files touched by this commit (3558)
Log message:
Recursive bump for perl5-5.28.0
   2016-04-09 14:51:50 by Adam Ciarcinski | Files touched by this commit (90) | Package updated
Log message:
The PostgreSQL Global Development Group has released an update to all supported \ 
versions of our database system, including 9.5.2, 9.4.7, 9.3.12, 9.2.16, and \ 
9.1.21. This release fixes two security issues and one index corruption issue in \ 
version 9.5. It also contains a variety of bug fixes for earlier versions. Users \ 
of PostgreSQL 9.5.0 or 9.5.1 should update as soon as possible.

This release closes security hole CVE-2016-2193, where a query plan might get \ 
reused for more than one ROLE in the same session. This could cause the wrong \ 
set of Row Level Security (RLS) policies to be used for the query.

The update also fixes CVE-2016-3065, a server crash bug triggered by using \ 
pageinspect with BRIN index pages. Since an attacker might be able to expose a \ 
few bytes of server memory, this crash is being treated as a security issue.
   2016-03-05 12:29:49 by Jonathan Perkin | Files touched by this commit (1813) | Package updated
Log message:
Bump PKGREVISION for security/openssl ABI bump.
   2015-01-14 22:01:20 by Adam Ciarcinski | Files touched by this commit (76)
Log message:
PostgreSQL 9.4.0:
This release adds many new features which enhance PostgreSQL's flexibility, \ 
scalability and performance for many different types of database users, \ 
including improvements to JSON support, replication and index performance.