kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/postgresql10/distinfo

20 lines
1.4 KiB
Text
Raw Normal View History

postgresql: updated to 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24 PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24 Security Issues * CVE-2020-25695: Multiple features escape "security restricted operation" sandbox * CVE-2020-25694: Reconnection can downgrade connection security settings * CVE-2020-25696: psql's \gset allows overwriting specially treated variables Bug Fixes and Improvements This update also fixes over 65 bugs that were reported in the last several months. Some of these issues only affect version 13, but may also apply to other supported versions. Some of these fixes include: Fix a breakage in the replication protocol by ensuring that two "command completion" events are expected for START_REPLICATION. Ensure fsync is called on the SLRU caches that PostgreSQL maintains. This prevents potential data loss due to an operating system crash. Fix ALTER ROLE usage for users with the BYPASSRLS permission. ALTER TABLE ONLY ... DROP EXPRESSION is disallowed on partitioned tables when there are child tables. Ensure that ALTER TABLE ONLY ... ENABLE/DISABLE TRIGGER does not apply to child tables. Fix for ALTER TABLE ... SET NOT NULL on partitioned tables to avoid a potential deadlock in parallel pg_restore. Fix handling of expressions in CREATE TABLE LIKE with inheritance. DROP INDEX CONCURRENTLY is disallowed on partitioned tables. Allow LOCK TABLE to succeed on a self-referential view instead of throwing an error. Several fixes around statistics collection and progress reporting for REINDEX CONCURRENTLY. Ensure that GENERATED columns are updated when any columns they depend on are updated via a rule or an updatable view. Support hash partitioning with text array columns as partition keys. Allow the jsonpath .datetime() method to accept ISO 8601-format timestamps. During a "smart" shutdown, ensure background processes are not terminated until all foreground client sessions are completed, fixing an issue that broke the processing of parallel queries. Several fixes for the query planner and optimizer. Ensure that data is de-toasted before being inserted into a BRIN index. This could manifest itself with errors like "missing chunk number 0 for toast value NNN". If you have seen a similar error in an existing BRIN index, you should be able to correct it by using REINDEX on the index. Fix the output of EXPLAIN to have the correct XML tag nesting for incremental sort plans. Several fixes for memory leaks, including ones involving RLS policies, using CALL with PL/pgSQL, SIGHUP processing a configuration parameter that cannot be applied without a restart, and an edge-case for index lookup for a partition. libpq can now support arbitrary-length lines in the .pgpass file. On Windows, psql now reads the output of a backtick command in text mode, not binary mode, so it can now properly handle newlines. Fix how pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb use complex connection-string parameters. When the \connect command of psql reuses connection parameters, ensure that all non-overridden parameters from a previous connection string are also re-used. Ensure that pg_dump collects per-column information about extension configuration tables, avoiding crashes when specifying --inserts. Ensure that parallel pg_restore processes foreign keys referencing partitioned tables in the correct order. Several fixes for contrib/pgcrypto, including a memory leak fix.
2020-11-16 13:15:02 +01:00
$NetBSD: distinfo,v 1.17 2020/11/16 12:15:02 adam Exp $
postgresql10: added version 10.0 Major enhancements in PostgreSQL 10 include: Logical replication using publish/subscribe Declarative table partitioning Improved query parallelism Significant general performance improvements Stronger password authentication based on SCRAM-SHA-256 Improved monitoring and control The above items are explained in more detail in the sections below.
2017-10-23 22:33:49 +02:00
postgresql: updated to 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24 PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24 Security Issues * CVE-2020-25695: Multiple features escape "security restricted operation" sandbox * CVE-2020-25694: Reconnection can downgrade connection security settings * CVE-2020-25696: psql's \gset allows overwriting specially treated variables Bug Fixes and Improvements This update also fixes over 65 bugs that were reported in the last several months. Some of these issues only affect version 13, but may also apply to other supported versions. Some of these fixes include: Fix a breakage in the replication protocol by ensuring that two "command completion" events are expected for START_REPLICATION. Ensure fsync is called on the SLRU caches that PostgreSQL maintains. This prevents potential data loss due to an operating system crash. Fix ALTER ROLE usage for users with the BYPASSRLS permission. ALTER TABLE ONLY ... DROP EXPRESSION is disallowed on partitioned tables when there are child tables. Ensure that ALTER TABLE ONLY ... ENABLE/DISABLE TRIGGER does not apply to child tables. Fix for ALTER TABLE ... SET NOT NULL on partitioned tables to avoid a potential deadlock in parallel pg_restore. Fix handling of expressions in CREATE TABLE LIKE with inheritance. DROP INDEX CONCURRENTLY is disallowed on partitioned tables. Allow LOCK TABLE to succeed on a self-referential view instead of throwing an error. Several fixes around statistics collection and progress reporting for REINDEX CONCURRENTLY. Ensure that GENERATED columns are updated when any columns they depend on are updated via a rule or an updatable view. Support hash partitioning with text array columns as partition keys. Allow the jsonpath .datetime() method to accept ISO 8601-format timestamps. During a "smart" shutdown, ensure background processes are not terminated until all foreground client sessions are completed, fixing an issue that broke the processing of parallel queries. Several fixes for the query planner and optimizer. Ensure that data is de-toasted before being inserted into a BRIN index. This could manifest itself with errors like "missing chunk number 0 for toast value NNN". If you have seen a similar error in an existing BRIN index, you should be able to correct it by using REINDEX on the index. Fix the output of EXPLAIN to have the correct XML tag nesting for incremental sort plans. Several fixes for memory leaks, including ones involving RLS policies, using CALL with PL/pgSQL, SIGHUP processing a configuration parameter that cannot be applied without a restart, and an edge-case for index lookup for a partition. libpq can now support arbitrary-length lines in the .pgpass file. On Windows, psql now reads the output of a backtick command in text mode, not binary mode, so it can now properly handle newlines. Fix how pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb use complex connection-string parameters. When the \connect command of psql reuses connection parameters, ensure that all non-overridden parameters from a previous connection string are also re-used. Ensure that pg_dump collects per-column information about extension configuration tables, avoiding crashes when specifying --inserts. Ensure that parallel pg_restore processes foreign keys referencing partitioned tables in the correct order. Several fixes for contrib/pgcrypto, including a memory leak fix.
2020-11-16 13:15:02 +01:00
SHA1 (postgresql-10.15.tar.bz2) = 3d688f05d2de7c9ed89ef6be8d33906a4e7a833d
RMD160 (postgresql-10.15.tar.bz2) = d913c1f991c16bae10db941d9b9fdb0d31f92ebe
SHA512 (postgresql-10.15.tar.bz2) = 88fe322a8691692f8c1b8ca7f7a5a035c399c1d2a0e6276b60863f2c0cb8e4857b041d7364641e0738438aee0836688e712b9c176ac454ee98386dfd18754636
Size (postgresql-10.15.tar.bz2) = 19089779 bytes
postgresql10: added version 10.0 Major enhancements in PostgreSQL 10 include: Logical replication using publish/subscribe Declarative table partitioning Improved query parallelism Significant general performance improvements Stronger password authentication based on SCRAM-SHA-256 Improved monitoring and control The above items are explained in more detail in the sections below.
2017-10-23 22:33:49 +02:00
SHA1 (patch-config_missing) = c2d7d742922ba6861e7660c75b7b53f09e564813
postgresql: updated to 10.2, 9.6.7, 9.5.11, 9.4.16, and 9.3.21 This release fixes two security issues. This release also fixes issues with VACUUM, GIN indexes, and hash indexes that could lead to data corruption, as well as fixes for using parallel queries and logical replication. Security Issues * CVE-2018-1052: Fix the processing of partition keys containing multiple expressions * CVE-2018-1053: Ensure that all temporary files made with "pg_upgrade" are non-world-readable Bug Fixes and Improvements * Fix crash and potential disclosure of backend memory when processing partition keys containing multiple expressions * Fix potential disclosure of temporary files containing database passwords created by pg_upgrade by not allowing these files to be world-accessible * Fix cases where VACUUM would not remove dead rows if they were updated while "key-share" locked, leading to potential data corruption * Fix for GIN indexes to prevent bloat by ensuring the pending-insertions list is cleaned up by VACUUM * Fix potential index corruption with hash indexes due to failure to mark metapages as dirty * Fix several potential crash scenarios for parallel queries, including when a bitmap heap scan cannot allocate memory * Fix several potential hang-ups in parallel queries, including when a parallel worker fails to start * Fix collection of EXPLAIN statistics from parallel workers * Prevent fake deadlock failures when multiple sessions are running CREATE INDEX CONCURRENTLY * Fix for trigger behavior when using logical replication * Several fixes for "walsender" functionality to improve stability as well as visibility into the replication process * Fix logical decoding to correctly clean up disk files for crashed transactions * Several fixes for identity columns, including disallowing identity columns on tables derived from composite types and partitions * Fix handling of list partitioning constraints for partition keys of boolean and array types * Fix incorrectly generated plans for UPDATE and DELETE queries when a table has a mix of inherited regular and foreign child tables * Fix incorrect query results from cases involving GROUPING SETS when used with flattened subqueries * Fix UNION/INTERSECT/EXCEPT over zero columns, e.g. "SELECT UNION SELECT;" * Several fixes for subqueries within a LATERAL subquery * Several improvements for query planning estimation * Allow a client that supports SCRAM channel binding, such as a future version of PostgreSQL or libpq, to connect to a PostgreSQL 10 server * Fix sample INSTR() functions used to help transition from Oracle(r) PL/SQL to PostgreSQL PL/pgSQL to correctly match Oracle functional behavior * Fix pg_dump to make permissions (ACL), security label, and comment entries reliably identifiable in archive outputs * Modify behavior for contrib/cube's "cube ~> int" operator to make it compatible with KNN search. This is a backwards incompatible change and any expression indexes or materialized views using this operator will need to be reindexed and refreshed, respectively. * Several fixes in contrib/postgres_fdw to prevent query planner errors * Added modern examples of auto-start scripts for PostgreSQL on macOS in the contrib/start-scripts/macos directory * Several fixes for Windows, including postmaster startup and compatibility with libperl * Spinlock fixes and support for Motorola 68K and 88K architectures
2018-02-08 21:53:56 +01:00
SHA1 (patch-config_perl.m4) = b3393d0f28e97f89ae20297d85553c508b3896bb
SHA1 (patch-configure) = b0a758023b3b263ff51b154d0da32cf02520c6cd
postgresql10: added version 10.0 Major enhancements in PostgreSQL 10 include: Logical replication using publish/subscribe Declarative table partitioning Improved query parallelism Significant general performance improvements Stronger password authentication based on SCRAM-SHA-256 Improved monitoring and control The above items are explained in more detail in the sections below.
2017-10-23 22:33:49 +02:00
SHA1 (patch-contrib_dblink_dblink.c) = a6f87ab9f2c28a72608d70267b71bd77437b0921
SHA1 (patch-src_Makefile.global.in) = 335b57afff23a9684ab0a09257665810c1ba2d1e
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-11-09 19:12:23 +01:00
SHA1 (patch-src_Makefile.shlib) = 74ab026a457a4789a1aa1d6423d88ce4a2db7a2e
postgresql10: added version 10.0 Major enhancements in PostgreSQL 10 include: Logical replication using publish/subscribe Declarative table partitioning Improved query parallelism Significant general performance improvements Stronger password authentication based on SCRAM-SHA-256 Improved monitoring and control The above items are explained in more detail in the sections below.
2017-10-23 22:33:49 +02:00
SHA1 (patch-src_backend_Makefile) = 91aa620b3a26f3da66c22aef78611a352a8793b6
SHA1 (patch-src_backend_utils_adt_datetime.c) = d1ea70986634d3bfb663eff789425252656e1289
SHA1 (patch-src_interfaces_ecpg_pgtypeslib_interval.c) = a15012ae34d4ecd1eb2bc29e4d2c40098ea236fd
SHA1 (patch-src_interfaces_libpq_Makefile) = 61bcf84eb69b6ec9faabab0b61913766f4b20f8c
SHA1 (patch-src_makefiles_Makefile.solaris) = 0168f5bc105ffc89d5db40907a08966d8465f5a0
SHA1 (patch-src_pl_plperl_GNUmakefile) = 6ee3e431f46ce5c2a94df499504b2b8bd458bbef
postgresql: updated to 10.2, 9.6.7, 9.5.11, 9.4.16, and 9.3.21 This release fixes two security issues. This release also fixes issues with VACUUM, GIN indexes, and hash indexes that could lead to data corruption, as well as fixes for using parallel queries and logical replication. Security Issues * CVE-2018-1052: Fix the processing of partition keys containing multiple expressions * CVE-2018-1053: Ensure that all temporary files made with "pg_upgrade" are non-world-readable Bug Fixes and Improvements * Fix crash and potential disclosure of backend memory when processing partition keys containing multiple expressions * Fix potential disclosure of temporary files containing database passwords created by pg_upgrade by not allowing these files to be world-accessible * Fix cases where VACUUM would not remove dead rows if they were updated while "key-share" locked, leading to potential data corruption * Fix for GIN indexes to prevent bloat by ensuring the pending-insertions list is cleaned up by VACUUM * Fix potential index corruption with hash indexes due to failure to mark metapages as dirty * Fix several potential crash scenarios for parallel queries, including when a bitmap heap scan cannot allocate memory * Fix several potential hang-ups in parallel queries, including when a parallel worker fails to start * Fix collection of EXPLAIN statistics from parallel workers * Prevent fake deadlock failures when multiple sessions are running CREATE INDEX CONCURRENTLY * Fix for trigger behavior when using logical replication * Several fixes for "walsender" functionality to improve stability as well as visibility into the replication process * Fix logical decoding to correctly clean up disk files for crashed transactions * Several fixes for identity columns, including disallowing identity columns on tables derived from composite types and partitions * Fix handling of list partitioning constraints for partition keys of boolean and array types * Fix incorrectly generated plans for UPDATE and DELETE queries when a table has a mix of inherited regular and foreign child tables * Fix incorrect query results from cases involving GROUPING SETS when used with flattened subqueries * Fix UNION/INTERSECT/EXCEPT over zero columns, e.g. "SELECT UNION SELECT;" * Several fixes for subqueries within a LATERAL subquery * Several improvements for query planning estimation * Allow a client that supports SCRAM channel binding, such as a future version of PostgreSQL or libpq, to connect to a PostgreSQL 10 server * Fix sample INSTR() functions used to help transition from Oracle(r) PL/SQL to PostgreSQL PL/pgSQL to correctly match Oracle functional behavior * Fix pg_dump to make permissions (ACL), security label, and comment entries reliably identifiable in archive outputs * Modify behavior for contrib/cube's "cube ~> int" operator to make it compatible with KNN search. This is a backwards incompatible change and any expression indexes or materialized views using this operator will need to be reindexed and refreshed, respectively. * Several fixes in contrib/postgres_fdw to prevent query planner errors * Added modern examples of auto-start scripts for PostgreSQL on macOS in the contrib/start-scripts/macos directory * Several fixes for Windows, including postmaster startup and compatibility with libperl * Spinlock fixes and support for Motorola 68K and 88K architectures
2018-02-08 21:53:56 +01:00
SHA1 (patch-src_pl_plperl_plperl.h) = 64d5b891362c114bde5ec48e48bc4855b56ab516
Reference in a new issue Copy permalink