Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql10
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.12 / (download) - annotate - [select for diffs], Mon May 13 20:38:11 2019 UTC (12 days, 6 hours ago) by adam
CVS Tags: HEAD
Changes since 1.11: +2 -2 lines
Diff to previous 1.11 (colored)
postgresqlNN: updated to the latest PostgreSQL 11.3, 10.8, 9.6.13, 9.5.17, and 9.4.22 Released! The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 11.3, 10.8, 9.6.13, 9.5.17, and 9.4.22. This release fixes two security issues in the PostgreSQL server, a security issue found in two of the PostgreSQL Windows installers, and over 60 bugs reported over the last three months. Security Issues Four security vulnerabilities have been closed by this release: CVE-2019-10127: BigSQL Windows installer does not clear permissive ACL entries CVE-2019-10128: EnterpriseDB Windows installer does not clear permissive ACL entries Due to both the EnterpriseDB and BigSQL Windows installers not locking down the permissions of the PostgreSQL binary installation directory and the data directory, an unprivileged Windows user account and an unprivileged PostgreSQL account could cause the PostgreSQL service account to execute arbitrary code. This vulnerability is present in all supported versions of PostgreSQL for these installers, and possibly exists in older versions. Both sets of installers have fixed the permissions for these directories for both new and existing installations. If you have installed PostgreSQL on Windows using other methods, we advise that you check that your PostgreSQL binary directories are writable only to trusted users and that your data directories are only accessible to trusted users. The PostgreSQL project thanks Conner Jones for reporting this problem. CVE-2019-10129: Memory disclosure in partition routing Prior to this release, a user running PostgreSQL 11 can read arbitrary bytes of server memory by executing a purpose-crafted INSERT statement to a partitioned table. CVE-2019-10130: Selectivity estimators bypass row security policies PostgreSQL maintains statistics for tables by sampling data available in columns; this data is consulted during the query planning process. Prior to this release, a user able to execute SQL queries with permissions to read a given column could craft a leaky operator that could read whatever data had been sampled from that column. If this happened to include values from rows that the user is forbidden to see by a row security policy, the user could effectively bypass the policy. This is fixed by only allowing a non-leakproof operator to use this data if there are no relevant row security policies for the table. This issue is present in PostgreSQL 9.5, 9.6, 10, and 11. The PostgreSQL project thanks Dean Rasheed for reporting this problem. Bug Fixes and Improvements This update also fixes over 60 bugs that were reported in the last several months. Some of these issues affect only version 11, but many affect all supported versions. Some of these fixes include: Several catalog corruption fixes, including one related to running ALTER TABLE on a partitioned table Several fixes for partitioning Avoid server crash when an error occurs while trying to persist a cursor query across a transaction commit Avoid O(N^2) performance issue when rolling back a transaction that created many tables Fix possible „ŗ◊ńould not access status of transaction„ŗfailures in txid_status() Fix updatable views to handle explicit DEFAULT items in INSERT .. VALUES statements where there are multiple VALUES rows Fix CREATE VIEW to allow zero-column views Add missing support for the CREATE TABLE IF NOT EXISTS .. AS EXECUTE .. statement Ensure that sub-SELECTs appearing in row-level-security policy expressions are executed with the correct user's permissions Accept XML documents as valid values of type xml when xmloption is set to content, as required by SQL:2006 and later Fix incompatibility of GIN-index WAL records that were introduced in 11.2, 10.7, 9.6.12, 9.5.16, and 9.4.21 that affected replica servers running these versions reading in changes to GIN indexes from primary servers of older versions Several memory leak fixes as well as fixes to management of dynamic shared memory Relax panics on fsync and sync_file_range failures for certain cases where a failure indicated "operation not supported" Several fixes to the query planner, several of which should lead to planning improvements Fix race condition in which a hot-standby postmaster could fail to shut down after receiving a smart-shutdown request Several fixes for SCRAM authentication Fix handling of lc_time settings that imply an encoding different from the database's encoding Create the current_logfiles file with the same permissions as other files in the server's data directory Several ecpg fixes Make pg_verify_checksums verify that the data directory it's pointed at is of the right PostgreSQL version Several fixes for contrib/postgres_fdw, including one for remote partitions where an UPDATE could lead to incorrect results or a crash Several Windows fixes This update also contains tzdata release 2019a for DST law changes in Palestine and Metlakatla, plus historical corrections for Israel. Etc/UCT is now a backward-compatibility link to Etc/UTC, instead of being a separate zone that generates the abbreviation UCT, which nowadays is typically a typo. PostgreSQL will still accept UCT as an input zone abbreviation, but it won't output it.
Revision 1.11 / (download) - annotate - [select for diffs], Sun Feb 17 08:26:11 2019 UTC (3 months ago) by adam
CVS Tags: pkgsrc-2019Q1-base, pkgsrc-2019Q1
Changes since 1.10: +2 -2 lines
Diff to previous 1.10 (colored)
postgresqlNN: updated to 11.2, 10.7, 9.6.12, 9.5.16, and 9.4.21 PostgreSQL 11.2, 10.7, 9.6.12, 9.5.16, and 9.4.21 Released! This release changes the behavior in how PostgreSQL interfaces with fsync() and includes fixes for partitioning and over 70 other bugs that were reported over the past three months. Fix handling of unique indexes with INCLUDE columns on partitioned tables Ensure that NOT NULL constraints of a partitioned table are honored within its partitions Several fixes for constraints on partitioned tables Fix problems with applying ON COMMIT DROP and ON COMMIT DELETE ROWS to partitioned tables and tables with inheritance children Disallow COPY FREEZE on partitioned tables Several fixes for the ALTER TABLE .. ADD COLUMN with a non-nullable default feature, including a possible index corruption case Several fixes in GIN indexes, including avoiding a deadlock with vacuuming and concurrent index insertions (which partially reverts a performance improvement introduced in PostgreSQL 10) Fix possible crashes in logical replication when index expressions or predicates are in use Several fixes for the write-ahead log (WAL) Fix possible crash in UPDATE with a multiple SET clause using a sub-SELECT Fix crash when zero rows are provided to json[b]_populate_recordset() or json[b]_to_recordset() Several fixes related to collation handling, including the parsing of collation-sensitive expressions in the arguments of a CALL statement Several fixes for the query planner, including an improvement to planning speed for large inheritance or partitioning table groups Several fixes for TRUNCATE Ensure ALTER TABLE ONLY ADD COLUMN IF NOT EXISTS is processed correctly Allow UNLISTEN in hot-standby (replica) mode Fix parsing of space-separated lists of host names in the ldapserver parameter of LDAP authentication entries in pg_hba.conf Several fixes for ecpg Several fixes for psql, including having \g target work with COPY TO STDOUT The random number generation for pgbench is now fully deterministic and platform-independent when --random-seed=N is specified Fix pg_basebackup and pg_verify_checksums to appropriately ignore temporary files Several fixes for pg_dump, including having ALTER INDEX SET STATISTICS commands present Prevent false index-corruption reports from contrib/amcheck caused by inline-compressed data Support new Makefile variables to help with building extensions
Revision 1.10 / (download) - annotate - [select for diffs], Fri Nov 9 18:12:23 2018 UTC (6 months, 2 weeks ago) by adam
CVS Tags: pkgsrc-2018Q4-base, pkgsrc-2018Q4
Changes since 1.9: +2 -2 lines
Diff to previous 1.9 (colored)
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.
Revision 1.9 / (download) - annotate - [select for diffs], Fri Aug 10 11:56:10 2018 UTC (9 months, 2 weeks ago) by adam
CVS Tags: pkgsrc-2018Q3-base, pkgsrc-2018Q3
Changes since 1.8: +2 -2 lines
Diff to previous 1.8 (colored)
postgresql: updated to 10.5, 9.6.10, 9.5.14, 9.4.19, 9.3.24 The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.5, 9.6.10, 9.5.14, 9.4.19, 9.3.24. This release fixes two security issues as well as bugs reported over the last three months. SECURITY ISSUES: CVE-2018-10915: CERTAIN HOST CONNECTION PARAMETERS DEFEAT CLIENT-SIDE SECURITY DEFENSES CVE-2018-10925: MEMORY DISCLOSURE AND MISSING AUTHORIZATION IN INSERT ... ON CONFLICT DO UPDATE BUG FIXES AND IMPROVEMENTS Several fixes related to VACUUM, including an issue that could lead to data corruption in certain system catalog tables Several fixes for replaying write-ahead logs, including a case where a just-promoted standby server would not restart if it crashed before its first post-recovery checkpoint Several performance improvements for replaying write-ahead logs Several fixes for logical replication and logical decoding, including ensuring logical WAL senders are reporting the streaming state correctly Allow replication slots to be dropped in single-user mode Fix to have variance and similar aggregate functions return accurate results when executed using parallel query Fix SQL-standard FETCH FIRST syntax to allow parameters ($n), as the standard expects Fix to ensure that a process doing a parallel index scan will respond to signals, such as one to abort a query Fix EXPLAIN's accounting for resource usage, particularly buffer accesses, in parallel workers Several fixes for the query planner including improving the cost estimates for hash-joins and choosing to use indexes for mergejoins on composite type columns Fix performance regression related to POSIX semaphores for multi-CPU systems running Linux or FreeBSD Fix for GIN indexes that could lead to an assertion failure after a pg_upgrade from a version before PostgreSQL 9.4 Fix for SHOW ALL to display superuser configuration settings to roles that are allowed to read all settings Fix issue where COPY FROM .. WITH HEADER would drop a line after every 4,294,967,296 lines processed Several fixes for XML support, including using the document node as the context for XPath queries as defined in the SQL standard, which affects the xpath and xpath_exists functions, as well as XMLTABLE Fix libpq for certain cases where hostaddr is used Several ecpg fixes for Windows Fix password prompting in Windows client programs so that echo is properly disabled Several pg_dump fixes, including correctly outputting REPLICA IDENTITY properties for constraint indexes Make pg_upgrade check that the old server was shut down cleanly
Revision 1.8 / (download) - annotate - [select for diffs], Sun May 13 08:13:46 2018 UTC (12 months, 1 week ago) by adam
CVS Tags: pkgsrc-2018Q2-base, pkgsrc-2018Q2
Changes since 1.7: +2 -2 lines
Diff to previous 1.7 (colored)
postgresql: updated to 10.4, 9.6.9, 9.5.13, 9.4.18, 9.3.23 SECURITY ISSUES One security vulnerability has been closed by this release: CVE-2018-1115: Too-permissive access control list on function pg_logfile_rotate() Please see the "Updating" section below for post-update steps. BUG FIXES AND IMPROVEMENTS This update also fixes over 50 bugs reported in the last several months. Some of these issues affect only version 10, but many affect all supported versions. These fixes include: Fix incorrect volatility and parallel-safety markings on several built-in functions to ensure correct query planning optimizations Several fixes for partitioning, including potential crashes as well as allowing TRUE and FALSE to be used as partition bounds Fix where a new TOAST value could be assigned to a dead-but-not-yet-vacuumed TOAST OID, which would result in an error similar to "unexpected chunk number 0 (expected 1) for toast value nnnnn" Fix "CREATE TABLE ... LIKE" with bigint identity columns on 32-bit platforms Fix memory leak within the runtime of a query that repeatedly executes hash joins Several crash fixes around queries using GROUPING SET Avoid failure if a query-cancel or session-termination interrupt occurs while committing a prepared transaction Reduce locking during autovacuum worker scheduling, which prevents loss of potential worker concurrency Fix possible slow execution of REFRESH MATERIALIZED VIEW CONCURRENTLY Several fixes around query plans that use "index-only" scans Avoid deadlocks in concurrent CREATE INDEX CONCURRENTLY commands that are run under SERIALIZABLE or REPEATABLE READ transaction isolation Several fixes for SP-GiST indexes, including one collation-aware searches on text columns Fixes related to counting the number of tuples in partial GiST, SP-GiST, and Bloom indexes Several fixes for logical decoding and replication Fix misquoting of values for list-valued GUC variables (e.g. local_preload_libraries, session_preload_libraries, shared_preload_libraries, temp_tablespaces) in dumps Several fixes for pg_stat_activity Several fixes for ecpg Fix for pg_recvlogical to ensure compatibility with PostgreSQL versions released before 10 Several fixes for pg_rewind
Revision 1.7 / (download) - annotate - [select for diffs], Fri Mar 2 17:11:12 2018 UTC (14 months, 3 weeks ago) by adam
CVS Tags: pkgsrc-2018Q1-base, pkgsrc-2018Q1
Changes since 1.6: +2 -2 lines
Diff to previous 1.6 (colored)
postgresqlNN: updated to 10.3, 9.6.8, 9.5.12, 9.4.17, 9.3.22 PostgreSQL 10.3, 9.6.8, 9.5.12, 9.4.17, and 9.3.22: The purpose of this release is to address CVE-2018-1058, which describes how a user can create like-named objects in different schemas that can change the behavior of other users' queries and cause unexpected or malicious behavior, also known as a "trojan-horse" attack. Most of this release centers around added documentation that describes the issue and how to take steps to mitigate the impact on PostgreSQL databases.
Revision 1.6 / (download) - annotate - [select for diffs], Thu Feb 8 20:53:56 2018 UTC (15 months, 2 weeks ago) by adam
Changes since 1.5: +2 -2 lines
Diff to previous 1.5 (colored)
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
Revision 1.5 / (download) - annotate - [select for diffs], Fri Dec 15 16:52:23 2017 UTC (17 months, 1 week ago) by dholland
CVS Tags: pkgsrc-2017Q4-base, pkgsrc-2017Q4
Changes since 1.4: +0 -2 lines
Diff to previous 1.4 (colored)
PR 52787: fix postgres kerberos handling. Tuck the kerberos support (whether "kerberos" or "gssapi") within an option so it can be turned off. For 92/93 this is the existing "kerberos" option; for 94+ this is the "gssapi" option instead, to satisfy the one person who cares about the distinction. For postgresql92 and 93 the kerberos option is now on by default (it wasn't before, only the "gssapi" code has been on by default since the last update) -- it isn't clear to what extent this may make the binary packages different so precautionary revbumps will be coming in a moment. Technically for 92/93 the "gssapi" code could be attached to a separate "gssapi" option so as to make the existing behavior entirely unchanged, but this seems likely to be confusing in the long run and thus not a good idea.
Revision 1.4 / (download) - annotate - [select for diffs], Thu Dec 7 14:19:32 2017 UTC (17 months, 2 weeks ago) by adam
Changes since 1.3: +2 -1 lines
Diff to previous 1.3 (colored)
postgresql: removed obsolete "kerberos" option; fix for #52787
Revision 1.3 / (download) - annotate - [select for diffs], Mon Nov 13 09:33:31 2017 UTC (18 months, 1 week ago) by adam
Changes since 1.2: +5 -8 lines
Diff to previous 1.2 (colored)
postgresql: updated to the latest The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, and 9.2.24. This release fixes three security issues. This release also fixes issues found in BRIN indexing, logical replication and other bugs reported over the past three months. All users using the affected versions of PostgreSQL should update as soon as possible. If you use BRIN indexes or contrib/start-scripts, please see the release notes for additional post-upgrade steps. Security Issues Three security vulnerabilities have been fixed by this release: CVE-2017-12172: Start scripts permit database administrator to modify root-owned files CVE-2017-15098: Memory disclosure in JSON functions CVE-2017-15099: INSERT ... ON CONFLICT DO UPDATE fails to enforce SELECT privileges 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 10, but many affect all supported versions: Fix a race condition in BRIN indexing that could cause some rows to not be included in the indexing. Fix crash when logical decoding is invoked from a PL language function. Several fixes for logical replication. Restored behavior for CTEs attached to INSERT/UPDATE/DELETE statements to pre-version 10. Prevent low-probability crash in processing of nested trigger firings. Do not evaluate an aggregate function's argument expressions when the conditions in the FILTER clause evaluate to FALSE. This complies with SQL-standard behavior. Fix incorrect query results when multiple GROUPING SETS columns contain the same simple variable. Fix memory leak over the lifespan of a query when evaluating a set-returning function from the target list in a SELECT. Several fixes for parallel query execution, including fixing a crash in the parallel execution of certain queries that contain a certain type of bitmap scan. Fix json_build_array(), json_build_object(), jsonb_build_array(), and jsonb_build_object() to handle explicit VARIADIC arguments correctly. Prevent infinite float values from being casted to the numeric type. Fix autovacuum's „ŗ◊ōork item„ŗlogic to prevent possible crashes and silent loss of work items. Several fixes for VIEWs around adding columns to the end of a view. Fix for hashability detection of range data types that are created by a user. Improvements on using extended statistics on columns for the purposes of query planning. Prevent idle_in_transaction_session_timeout from being ignored when a statement_timeout occurred earlier. Fix low-probability loss of NOTIFY messages due more than 2 billion transactions processing before any queries are executed in the session. Several file system interaction fixes. Correctly restore the umask setting when file creation fails in COPY or lo_export(). Fix pg_dump to ensure that it emits GRANT commands in a valid order. Fix pg_basebackup's matching of tablespace paths to canonicalize both paths before comparing to help improve Windows compatibility. Fix libpq to not require user's home directory to exist when trying to read the "~/.pgpass" file. Several fixes for ecpg.
Revision 1.2 / (download) - annotate - [select for diffs], Fri Nov 10 14:47:41 2017 UTC (18 months, 2 weeks ago) by fhajny
Changes since 1.1: +9 -1 lines
Diff to previous 1.1 (colored)
Make sure the --as-needed linker arg does not leak into the pgxs Makefiles on Darwin and SunOS where it's not supported. Bump PKGREVISION on *-client.
Revision 1.1 / (download) - annotate - [select for diffs], Mon Oct 23 20:33:49 2017 UTC (19 months ago) by adam
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.
This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.