Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql94
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Retired mysql55 and postgresql94 packages
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.
*: Recursive revision bump for openssl 1.1.1.
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.
Recursive bump for perl5-5.28.0
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.5.4, 9.4.9, 9.3.14, 9.2.18 and 9.1.23. This release fixes two security issues. It also patches a number of other bugs reported over the last three months. Users who rely on security isolation between database users should update as soon as possible. Other users should plan to update at the next convenient downtime. Security Issues --------------- Two security holes have been closed by this release: CVE-2016-5423: certain nested CASE expressions can cause the server to crash. CVE-2016-5424: database and role names with embedded special characters can allow code injection during administrative operations like pg_dumpall. The fix for the second issue also adds an option, -reuse-previous, to psql's \connect command. pg_dumpall will also refuse to handle database and role names containing line breaks after the update. For more information on these issues and how they affect backwards-compatibility, see the Release Notes. Bug Fixes and Improvements -------------------------- This update also fixes a number of bugs reported in the last few months. Some of these issues affect only version 9.5, but many affect all supported versions: Fix misbehaviors of IS NULL/IS NOT NULL with composite values Fix three areas where INSERT ... ON CONFLICT failed to work properly with other SQL features. Make INET and CIDR data types properly reject bad IPv6 values Prevent crash in "point ## lseg" operator for NaN input Avoid possible crash in pg_get_expr() Fix several one-byte buffer over-reads in to_number() Don't needlessly plan query if WITH NO DATA is specified Avoid crash-unsafe state in expensive heap_update() paths Fix hint bit update during WAL replay of row locking operations Avoid unnecessary "could not serialize access" with FOR KEY SHARE Avoid crash in postgres -C when the specified variable is a null string Fix two issues with logical decoding and subtransactions Ensure that backends see up-to-date statistics for shared catalogs Prevent possible failure when vacuuming multixact IDs in an upgraded database When a manual ANALYZE specifies columns, don't reset changes_since_analyze Fix ANALYZE's overestimation of n_distinct for columns with nulls Fix bug in b-tree mark/restore processing Fix building of large (bigger than shared_buffers) hash indexes Prevent infinite loop in GiST index build with NaN values Fix possible crash during a nearest-neighbor indexscan Fix "PANIC: failed to add BRIN tuple" error Prevent possible crash during background worker shutdown Many fixes for issues in parallel pg_dump and pg_restore Make pg_basebackup accept -Z 0 as no compression Make regression tests safe for Danish and Welsh locales
Update postgresql94 & related to PostGreSQL 9.4.9
Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.
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.
Bump PKGREVISION for security/openssl ABI bump.
Pullup ticket #4935 - requested by tnn databases/postgresql94: security fix Revisions pulled up: - databases/postgresql94-docs/PLIST 1.7 - databases/postgresql94-plperl/Makefile 1.4 - databases/postgresql94/Makefile 1.3 - databases/postgresql94/Makefile.common 1.7 - databases/postgresql94/distinfo 1.9 --- Module Name: pkgsrc Committed By: tnn Date: Thu Feb 25 01:38:56 UTC 2016 Modified Files: pkgsrc/databases/postgresql94: Makefile.common distinfo pkgsrc/databases/postgresql94-docs: PLIST pkgsrc/databases/postgresql94-plperl: Makefile Log Message: Update to PostgreSQL 9.4.6 (2016-02-11) Heads up: For upgrading past 9.4.5, users of jsonb_path_ops GIN indexes should perform a REINDEX, because of a hash calculation fix. This release fixes two security issues, as well as several bugs found over the last four months. CVE-2016-0773 Unicode regular expression buffer overflow CVE-2016-0766 PL/Java privilege escalation --- Module Name: pkgsrc Committed By: tnn Date: Thu Feb 25 01:46:57 UTC 2016 Modified Files: pkgsrc/databases/postgresql94: Makefile Log Message: drop PKGREVISION after update
drop PKGREVISION after update
Recursive PKGREVISION bump for all packages mentioning 'perl', having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0.
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.