![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql95
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.39, Mon May 24 07:42:01 2021 UTC (2 years, 10 months ago) by adam
Branch: MAIN
CVS Tags: HEAD
Changes since 1.38: +1 -1
lines
FILE REMOVED
postgresql95: removed; EOL
Revision 1.38 / (download) - annotate - [select for diffs], Fri May 7 06:58:56 2021 UTC (2 years, 11 months ago) by nia
Branch: MAIN
Changes since 1.37: +6 -1
lines
Diff to previous 1.37 (colored) to selected 1.12 (colored)
postgresql*: explicitly mark BROKEN on Alpha Support for Alpha was removed in 2014. This removed the spinlock and memory barrier implementations, meaning Postgresql on Alpha no longer compiles cleanly with the default options. According to the commit message the code was "unlikely to currently work correctly". Enthusiasts may wish to re-add Alpha support, but it should likely only be done with proper testing to avoid data loss in the case someone uses it.
Revision 1.37 / (download) - annotate - [select for diffs], Fri Apr 16 06:38:20 2021 UTC (3 years ago) by nia
Branch: MAIN
Changes since 1.36: +2 -1
lines
Diff to previous 1.36 (colored) to selected 1.12 (colored)
postgresql: ensure linux libuuid is buildlinked when needed
Revision 1.36 / (download) - annotate - [select for diffs], Thu Mar 18 15:04:55 2021 UTC (3 years, 1 month ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2021Q1-base,
pkgsrc-2021Q1
Changes since 1.35: +12 -1
lines
Diff to previous 1.35 (colored) to selected 1.12 (colored)
postgresql: fix buildling contrib/uuid-ossp; fixes for LLVM enabled; should fix #55803
Revision 1.35 / (download) - annotate - [select for diffs], Mon Feb 15 18:58:40 2021 UTC (3 years, 2 months ago) by adam
Branch: MAIN
Changes since 1.34: +2 -2
lines
Diff to previous 1.34 (colored) to selected 1.12 (colored)
postgresql: updated to 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25 The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25. This release closes two security vulnerabilities and fixes over 80 bugs reported over the last three months. Additionally, this is the final release of PostgreSQL 9.5. If you are running PostgreSQL 9.5 in a production environment, we suggest that you make plans to upgrade. For the full list of changes, please review the release notes. Security Issues CVE-2021-3393: Partition constraint violation errors leak values of denied columns Versions Affected: 11 - 13. A user having an UPDATE privilege on a partitioned table but lacking the SELECT privilege on some column may be able to acquire denied-column values from an error message. This is similar to CVE-2014-8161, but the conditions to exploit are more rare. The PostgreSQL project thanks Heikki Linnakangas for reporting this problem. CVE-2021-20229: Single-column SELECT privilege enables reading all columns Versions Affected: 13. A user having a SELECT privilege on an individual column can craft a special query that returns all columns of the table. Additionally, a stored view that uses column-level privileges will have incomplete column-usage bitmaps. In installations that depend on column-level permissions for security, it is recommended to execute CREATE OR REPLACE on all user-defined views to force them to be re-parsed. The PostgreSQL project thanks Sven Klemm for reporting this problem. Bug Fixes and Improvements This update fixes over 80 bugs that were reported in the last several months. Some of these issues only affect version 13, but could also apply to other supported versions. Some of these fixes include: Fix an issue with GiST indexes where concurrent insertions could lead to a corrupt index with entries placed in the wrong pages. You should REINDEX any affected GiST indexes. Fix CREATE INDEX CONCURRENTLY to ensure rows from concurrent prepared transactions are included in the index. Installations that have enabled prepared transactions should REINDEX any concurrently-built indexes. Fix for possible incorrect query results when a hash aggregation is spilled to disk. Fix edge case in incremental sort that could lead to sorting results incorrectly or a "retrieved too many tuples in a bounded sort" error. Avoid crash when a CALL or DO statement that performs a transaction rollback is executed via extended query protocol, such as from prepared statements. Fix a failure when a PL/pgSQL procedure used CALL on another procedure that has OUT parameters that executed a COMMIT or ROLLBACK. Remove errors from BEFORE UPDATE triggers on partitioned tables for restrictions that no longer apply. Several fixes for queries with joins that could lead to error messages such as "no relation entry for relid N" or "failed to build any N-way joins". Do not consider parallel-restricted or set-returning functions in an ORDER BY expressions when trying to parallelize sorts. Fix ALTER DEFAULT PRIVILEGES to handle duplicate arguments safely. Several fixes in behavior when wal_level is set to minimal, including when tables are rewritten within a transaction. Several fixes for CREATE TABLE LIKE. Ensure that allocated disk space for a dropped relation (e.g. a table) is released promptly when a transaction is committed. Fix progress reporting for CLUSTER. Fix handling of backslash-escaped multibyte characters in COPY FROM. Fix recently-introduced race conditions in LISTEN/NOTIFY queue handling. Allow the jsonb concatenation operator (||) to handle all combinations of JSON data types. Fix WAL-reading logic so that standbys can handle timeline switches correctly. This issue could have shown itself with errors like "requested WAL segment has already been removed". Several leak fixes for the walsender process around logical decoding and replication. Ensure that a nonempty value of krb_server_keyfile always overrides any setting of KRB5_KTNAME in the server environment Several fixes for GSS encryption support. Ensure the \connect command allows the use of a password in the connection_string argument. Fix assorted bugs with the \help command. Several fixes for pg_dump. Ensure that pg_rewind accounts for all WAL when rewinding a standby server. Fix memory leak in contrib/auto_explain. Ensure all postgres_fdw connections are closed if the a user mapping or foreign server object those connections depend on are dropped. Fix JIT compilation to be compatible with LLVM 11 and LLVM 12. This update also contains tzdata release 2021a for DST law changes in Russia (Volgograd zone) and South Sudan, plus historical corrections for Australia, Bahamas, Belize, Bermuda, Ghana, Israel, Kenya, Nigeria, Palestine, Seychelles, and Vanuatu. Notably, the Australia/Currie zone has been corrected to the point where it is identical to Australia/Hobart. For the full list of changes available, please review the release notes. PostgreSQL 9.5 is EOL This is the final release of PostgreSQL 9.5. If you are running PostgreSQL 9.5 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information.
Revision 1.34 / (download) - annotate - [select for diffs], Mon Nov 16 12:15:06 2020 UTC (3 years, 5 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2020Q4-base,
pkgsrc-2020Q4
Changes since 1.33: +2 -2
lines
Diff to previous 1.33 (colored) to selected 1.12 (colored)
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.
Revision 1.33 / (download) - annotate - [select for diffs], Fri Aug 14 06:56:24 2020 UTC (3 years, 8 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2020Q3-base,
pkgsrc-2020Q3
Changes since 1.32: +2 -2
lines
Diff to previous 1.32 (colored) to selected 1.12 (colored)
postgresql: updated to 12.4, 11.9, 10.14, 9.6.19, 9.5.23 PostgreSQL 12.4, 11.9, 10.14, 9.6.19, 9.5.23 Security Issues CVE-2020-14349: Uncontrolled search path element in logical replication. Versions Affected: 10 - 12. The PostgreSQL search_path setting determines schemas searched for tables, functions, operators, etc. The CVE-2018-1058 fix caused most PostgreSQL-provided client applications to sanitize search_path, but logical replication continued to leave search_path unchanged. Users of a replication publisher or subscriber database can create objects in the public schema and harness them to execute arbitrary SQL functions under the identity running replication, often a superuser. Installations having adopted a documented secure schema usage pattern are not vulnerable. The PostgreSQL project thanks Noah Misch for reporting this problem. CVE-2020-14350: Uncontrolled search path element in CREATE EXTENSION. Versions Affected: 9.5 - 12. The security team typically does not test unsupported versions, but this problem is quite old. When a superuser runs certain CREATE EXTENSION statements, users may be able to execute arbitrary SQL functions under the identity of that superuser. The attacker must have permission to create objects in the new extension's schema or a schema of a prerequisite extension. Not all extensions are vulnerable. In addition to correcting the extensions provided with PostgreSQL, the PostgreSQL Global Development Group is issuing guidance for third-party extension authors to secure their own work. Bug Fixes and Improvements This update also fixes over 50 bugs that were reported in the last several months. Some of these issues affect only version 12, but many affect all supported versions. Some of these fixes include: Fix edge cases in partition pruning involving multiple partition key columns with multiple or no constraining WHERE clauses. Several fixes for query planning and execution involving partitions. Fix for determining when to execute a column-specific UPDATE trigger on a logical replication subscriber. pg_replication_slot_advance() now updates the oldest xmin and LSN values, as the failure to do this could prevent resources (e.g. WAL files) from being cleaned up. Fix a performance regression in ts_headline(). Ensure that pg_read_file() and related functions read until EOF is reached, which fixes compatibility with pipes and other virtual files. Forbid numeric NaN values in jsonpath computations, which do not exist in SQL nor JSON. Several fixes for NaN inputs with aggregate functions. This fixes a change in PostgreSQL 12 where NaN values caused the following aggregates to emit values of 0 instead of NaN: corr(), covar_pop(), regr_intercept(), regr_r2(), regr_slope(), regr_sxx(), regr_sxy(), regr_syy(), stddev_pop(), and var_pop(). time and timetz values fractionally greater than 24:00:00 are now rejected. Several fixes for EXPLAIN, including a fix for reporting resource usage when a plan uses parallel workers with "Gather Merge" nodes. Fix timing of constraint revalidation in ALTER TABLE that could lead to odd errors. Fix for REINDEX CONCURRENTLY that could prevent old values from being included in future logical decoding output. Fix for LATERAL references that could potentially cause crashes during query execution. Use the collation specified for a query when estimating operator costs Fix conflict-checking anomalies in SERIALIZABLE transaction isolation mode. Ensure checkpointer process discards file sync requests when fsync is off Fix issue where pg_control could be written out with an inconsistent checksum, which could lead to the inability to restart the database if it crashed before the next pg_control update. Ensure that libpq continues to try to read from the database connection socket after a write failure, as this allows the connection to collect any final error messages from the server. Report out-of-disk-space errors properly in pg_dump and pg_basebackup Several fixes for pg_restore, including a fix for parallel restore on tables that have both table-level and column-level privileges. Fix for pg_upgrade to ensure it runs with vacuum_defer_cleanup_age set to 0. Fix how pg_rewind handles just-deleted files in the source data directory Fix failure to initialize local state correctly in contrib/dblink, which could lead to dblink_close() issuing an unexpected COMMIT on the remote server. Change contrib/amcheck to not report about deleted index pages that are empty, as this is normal during WAL replay.
Revision 1.32 / (download) - annotate - [select for diffs], Fri Aug 7 19:39:40 2020 UTC (3 years, 8 months ago) by maya
Branch: MAIN
Changes since 1.31: +2 -1
lines
Diff to previous 1.31 (colored) to selected 1.12 (colored)
postgresql*: use PG_TEMPLATE=freebsd on dragonflybsd. From Aleksej Lebedev which specified it fixes postgresql12.
Revision 1.31 / (download) - annotate - [select for diffs], Fri May 15 09:45:01 2020 UTC (3 years, 11 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2020Q2-base,
pkgsrc-2020Q2
Changes since 1.30: +2 -2
lines
Diff to previous 1.30 (colored) to selected 1.12 (colored)
postgresqlNN: updated to 12.3, 11.8, 10.13, 9.6.18, and 9.5.22 PostgreSQL 12.3, 11.8, 10.13, 9.6.18, and 9.5.22 Released! Posted on 2020-05-14 by PostgreSQL Global Development Group The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 12.3, 11.8, 10.13, 9.6.18, and 9.5.22. This release fixes one security issue found in the PostgreSQL server and over 75 bugs reported over the last three months. Please plan to update at your earliest convenience. Security Issues CVE-2020-10733: Windows installer runs executables from uncontrolled directories. Versions Affected: 9.5 - 12. The security team does not test unsupported versions, but this issue existed before PostgreSQL 9.5. The Windows installer for PostgreSQL invokes system-provided executables that do not have fully-qualified paths. Executables in the directory where the installer loads or the current working directory take precedence over the intended executables. An attacker having permission to add files into one of those directories can use this to execute arbitrary code with the installer's administrative rights. The PostgreSQL project thanks Hou JingYi (@hjy79425575) for reporting this problem. 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: Several fixes for GENERATED columns, including an issue where it was possible to crash or corrupt data in a table when the output of the generated column was the exact copy of a physical column on the table, e.g. if the expression called a function which could return its own input. Several fixes for ALTER TABLE, including ensuring the SET STORAGE directive is propagated to a table's indexes. Fix a potential race condition when using DROP OWNED BY while another session is deleting the same objects. Allow for a partition to be detached when it has inherited ROW triggers. Several fixes for REINDEX CONCURRENTLY, particularly with issues when a REINDEX CONCURRENTLY operation fails. Fix crash when COLLATE is applied to an uncollatable type in a partition bound expression. Fix performance regression in floating point overflow/underflow detection. Several fixes for full text search, particularly with phrase searching. Fix query-lifespan memory leak for a set-returning function used in a query's FROM clause. Several reporting fixes for the output of VACUUM VERBOSE. Allow input of type circle to accept the format (x,y),r, which is specified in the documentation. Allow for the get_bit() and set_bit() functions to not fail on bytea strings longer than 256MB. Avoid premature recycling of WAL segments during crash recovery, which could lead to WAL segments being recycled before being archived. Avoid attempting to fetch nonexistent WAL files from archive storage during recovery by skipping irrelevant timelines. Several fixes for logical replication and replication slots. Fix several race conditions in synchronous standby management, including one that occurred when changing the synchronous_standby_names setting. Several fixes for GSSAPI support, include a fix for a memory leak that occurred when using GSSAPI encryption. Ensure that members of the pg_read_all_stats role can read all statistics views. Fix performance regression in information_schema.triggers view. Fix memory leak in libpq when using sslmode=verify-full. Fix crash in psql when attempting to re-establish a failed connection. Allow tab-completion of the filename argument to \gx command in psql. Add pg_dump support for ALTER ... DEPENDS ON EXTENSION. Several other fixes for pg_dump, which include dumping comments on RLS policies and postponing restore of event triggers until the end. Ensure pg_basebackup generates valid tar files. pg_checksums skips tablespace subdirectories that belong to a different PostgreSQL major version Several Windows compatibility fixes This update also contains tzdata release 2020a for DST law changes in Morocco and the Canadian Yukon, plus historical corrections for Shanghai. The America/Godthab zone has been renamed to America/Nuuk to reflect current English usage ; however, the old name remains available as a compatibility link. This also updates initdb's list of known Windows time zone names to include recent additions.
Revision 1.30 / (download) - annotate - [select for diffs], Fri Feb 14 17:06:44 2020 UTC (4 years, 2 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2020Q1-base,
pkgsrc-2020Q1
Changes since 1.29: +2 -2
lines
Diff to previous 1.29 (colored) to selected 1.12 (colored)
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.
Revision 1.29 / (download) - annotate - [select for diffs], Tue Nov 19 05:54:52 2019 UTC (4 years, 4 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2019Q4-base,
pkgsrc-2019Q4
Changes since 1.28: +2 -2
lines
Diff to previous 1.28 (colored) to selected 1.12 (colored)
postgresqlNN: updated to 12.1, 11.6, 10.11, 9.6.16, 9.5.20, and 9.4.25 PostgreSQL 12.1, 11.6, 10.11, 9.6.16, 9.5.20, and 9.4.25 Released! PostgreSQL 9.4 EOL Approaching PostgreSQL 9.4 will stop receiving fixes on February 13, 2020, which is the next planned cumulative update release. Please see our versioning policy for more information. Bug Fixes and Improvements This update also fixes over 50 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 crash that occurs when ALTER TABLE adds a column without a default value along with other changes that require a table rewrite Several fixes for REINDEX CONCURRENTLY. Fix for VACUUM that would cause it to fail under a specific case involving a still-running transaction. Fix for a memory leak that could occur when VACUUM runs on a GiST index. Fix for an error that occurred when running CLUSTER on an expression index. Fix failure for SET CONSTRAINTS ... DEFERRED on partitioned tables. Several fixes for the creation and dropping of indexes on partitioned tables. Fix for partition-wise joins that could lead to planner failures. Ensure that offset expressions in WINDOW clauses are processed when a query's expressions are manipulated. Fix misbehavior of bitshiftright() where it failed to zero out padding space in the last byte if the bit string length is not a multiple of 8. For how to correct your data, please see the "Updating" section. Ensure an empty string that is evaluated by the position() functions returns 1, as per the SQL standard. Fix for a parallel query failure when it is unable to request a background worker. Fix crash triggered by a case involving a BEFORE UPDATE trigger. Display the correct error when a query tries to access a TOAST table. Allow encoding conversion to succeed on strings with output up to 1GB. Previously there was hard limit of 0.25GB on the input string. Ensure that temporary WAL and history files are removed at the end of archive recovery. Avoid failure in archive recovery if recovery_min_apply_delay is enabled. Ignore restore_command, recovery_end_command, and recovery_min_apply_delay settings during crash recovery. Several fixes for logical replication, including a failure when the publisher and subscriber had different REPLICA IDENTITY columns set. Correctly timestamp replication messages for logical decoding, which in the broken case would lead to pg_stat_subscription.last_msg_send_time set to NULL. Several fixes for libpq, including one that improves PostgreSQL 12 compatibility. Several pg_upgrade fixes. Fix how a parallel restore handles foreign key constraints on partitioned tables to ensure they are not created too soon. pg_dump now outputs similarly named triggers and RLS policies in order based on table name, instead of OID. Fix pg_rewind to not update the contents of pg_control when using the --dry-run option. This update also contains tzdata release 2019c for DST law changes in Fiji and Norfolk Island. Historical corrections for Alberta, Austria, Belgium, British Columbia, Cambodia, Hong Kong, Indiana (Perry County), Kaliningrad, Kentucky, Michigan, Norfolk Island, South Korea, and Turkey.
Revision 1.28 / (download) - annotate - [select for diffs], Sat Nov 2 15:38:08 2019 UTC (4 years, 5 months ago) by rillig
Branch: MAIN
Changes since 1.27: +4 -4
lines
Diff to previous 1.27 (colored) to selected 1.12 (colored)
databases: align variable assignments pkglint -Wall -F --only aligned -r No manual corrections.
Revision 1.27 / (download) - annotate - [select for diffs], Mon Oct 7 19:28:29 2019 UTC (4 years, 6 months ago) by adam
Branch: MAIN
Changes since 1.26: +7 -7
lines
Diff to previous 1.26 (colored) to selected 1.12 (colored)
Remove unused files; cleanup
Revision 1.26 / (download) - annotate - [select for diffs], Sun Aug 11 11:40:11 2019 UTC (4 years, 8 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2019Q3-base,
pkgsrc-2019Q3
Changes since 1.25: +2 -2
lines
Diff to previous 1.25 (colored) to selected 1.12 (colored)
postgresqlNN: updated to 11.5, 10.10, 9.6.15, 9.5.19, 9.4.24
PostgreSQL 11.5, 10.10, 9.6.15, 9.5.19, 9.4.24
Security Issues
Four security vulnerabilities have been closed by this release:
CVE-2019-10208: TYPE in pg_temp executes arbitrary SQL during SECURITY DEFINER execution
Versions Affected: 9.4 - 11
Given a suitable SECURITY DEFINER function, an attacker can execute arbitrary SQL under the identity of the function owner. An attack requires EXECUTE permission on the function, which must itself contain a function call having inexact argument type match. For example, length('foo'::varchar) and length('foo') are inexact, while length('foo'::text) is exact. As part of exploiting this vulnerability, the attacker uses CREATE DOMAIN to create a type in a pg_temp schema. The attack pattern and fix are similar to that for CVE-2007-2138.
Writing SECURITY DEFINER functions continues to require
following the considerations noted in the documentation:
The PostgreSQL project thanks Tom Lane for reporting this problem.
CVE-2019-10209: Memory disclosure in cross-type comparison for hashed subplan
Versions Affected: 11
In a database containing hypothetical, user-defined hash equality operators, an attacker could read arbitrary bytes of server memory. For an attack to become possible, a superuser would need to create unusual operators. It is possible for operators not purpose-crafted for attack to have the properties that enable an attack, but we are not aware of specific examples.
The PostgreSQL project thanks Andreas Seltenreich for reporting this problem.
CVE-2019-10210: EnterpriseDB Windows installer writes PostgreSQL superuser password to unprotected temporary file
Versions Affected: The EnterpriseDB Windows installer for versions 9.4 - 11
The EnterpriseDB Windows installer writes a password to a temporary file in its installation directory, creates initial databases, and deletes the file. During those seconds while the file exists, a local attacker can read the PostgreSQL superuser password from the file.
The PostgreSQL project thanks Noah Misch for reporting this problem.
CVE-2019-10211: EnterpriseDB Windows installer bundled OpenSSL executes code from unprotected directory
Versions Affected: The EnterpriseDB Windows installer for versions 9.4 - 11
When the database server or libpq client library initializes SSL, libeay32.dll attempts to read configuration from a hard-coded directory. Typically, the directory does not exist, but any local user could create it and inject configuration. This configuration can direct OpenSSL to load and execute arbitrary code as the user running a PostgreSQL server or client. Most PostgreSQL client tools and libraries use libpq, and one can encounter this vulnerability by using any of them. This vulnerability is much like CVE-2019-5443, but it originated independently. One can work around the vulnerability by setting environment variable OPENSSL_CONF to "NUL:/openssl.cnf" or any other name that cannot exist as a file.
The PostgreSQL project thanks Daniel Gustafsson of the curl security team for reporting this problem.
Bug Fixes and Improvements
This update also fixes over 40 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:
Fix for ALTER TABLE ... ALTER COLUMN TYPE when multiple column types are modified in a single-command. This issue was introduced in the previous cumulative update (11.4, 10.9, 9.6.14, 9.5.18, 9.4.23, and 12 beta 2).
Ensure that partition key columns will not be dropped as the result of an "indirect drop," such as from a cascade from dropping the key column's data type (e.g. a custom data type). This fix is applied only to newly created partitioned tables: if you believe you have an affected partition table (e.g. one where the partition key uses a custom data type), you will need to either create a new table and move your data into it OR use pg_upgrade.
Prevent dropping a partitioned table's trigger if there are pending trigger events in child partitions. This particularly affects foreign key constraints, which are implemented by triggers.
Several additional fixes for partitioning, including a fix for partition pruning that could lead to inefficient queries.
Fix for parallel hash joins that could lead to duplicate result rows in EXISTS queries.
Several fixes for the query planner.
Several fixes for issues that would lead to query deadlocks.
Fix for multi-column foreign keys when rebuilding a foreign key constraint.
Prevent extended statistics from being built for inherited tables.
Fix for the canonicalization of date ranges that include -infinity/infinity endpoints to ensure the behavior matches the documentation.
Fix loss of fractional digits when converting very large money values to numeric.
Fix for PL/pgSQL functions that return composite types.
Make libpq ignore the \r carriage return in connection service files, which was causing connection failures in some edge cases.
Several fixes for psql, which includes avoiding incorrect tab completion options after SET variable =.
Improve reliability of contrib/amcheck's index verification.
Set initdb to prefer the timezone behavior defined by the C library instead of what is defined by localtime or posixrules. This ensures PostgreSQL uses the "real" timezone name instead of an artificial name.
Fix pg_dump to ensure that custom operator classes are dumped in the correct order to prevent creating an unrestorable dump.
Fix possible lockup in pgbench when using -R option.
Fix spinlock assembly code for MIPS CPUs so that it works on MIPS r6.
This update also contains tzdata release 2019b for DST law changes in Brazil, plus historical corrections for Hong Kong, Italy, and Palestine. This update also adds support for zic's new -b slim option to reduce the size of the installed zone files, though it is not currently being used by PostgreSQL.
Revision 1.25 / (download) - annotate - [select for diffs], Sun Jun 23 07:55:59 2019 UTC (4 years, 9 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2019Q2-base,
pkgsrc-2019Q2
Changes since 1.24: +2 -2
lines
Diff to previous 1.24 (colored) to selected 1.12 (colored)
postgresqlNN: updated to 11.4, 10.9, 9.6.14, 9.5.18, 9.4.23
PostgreSQL 11.4, 10.9, 9.6.14, 9.5.18, 9.4.23, and 12 Beta 2 Released!
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 11.4, 10.9, 9.6.14, 9.5.18, and 9.4.23, as well as the second beta of PostgreSQL 12. This release fixes one security issue and over 25 bugs since the previous cumulative update in May.
Security Issues
This release closes one security vulnerability:
CVE-2019-10164: Stack-based buffer overflow via setting a password
Versions affected: 10, 11, 12 beta.
Bug Fixes and Improvements
Fix assorted errors in run-time partition pruning that could lead to wrong answers in queries on partitioned tables
pg_dump now recreates table partitions using CREATE TABLE and ALTER TABLE .. ATTACH PARTITION rather than including PARTITION OF in the creation command
Improve how initdb determines which system time zone to select if there are equivalent names for the time zone. Also explicitly prefer UTC over UCT
Fix possible crash while trying to copy trigger definitions to a new partition
Fix failure of ALTER TABLE .. ALTER COLUMN TYPE when the table has a partial exclusion constraint
Fix failure of COMMENT command for comments on domains
Several fixes related to aggregation
Fix faulty generation of merge-append plans that could lead to "could not find pathkey item to sort" errors
Fix failures on dump/restore where views contained queries with duplicate join names
Fix conversion of JSON string literals to JSON-type output columns in json_to_record() and json_populate_record()
Fix incorrect optimization of {1,1} quantifiers in regular expressions
Fix issue for B-tree indexes during edge case failure involving columns covered with the INCLUDE clause, which manifests itself with errors during VACUUM. If you are affected by this issue, you will need to reindex the specific index
Fix race condition in check to see whether a pre-existing shared memory segment is still in use by a conflicting postmaster
Fix for the walreceiver process that avoids a crash or deadlock on shutdown
Avoid possible hang in libpq if using SSL and OpenSSL's pending-data buffer contains an exact multiple of 256 bytes
Fix ordering of GRANT commands emitted by pg_dump and pg_dumpall for databases and tablespaces
Fix misleading error reports from reindexdb
Ensure that vacuumdb returns correct status if an error occurs while using parallel jobs
Fix contrib/auto_explain to not cause problems in parallel queries, which resulted in failures like "could not find key N in shm TOC"
Account for possible data modifications by local BEFORE ROW UPDATE triggers in contrib/postgres_fdw
On Windows, avoid failure when the database encoding is set to SQL_ASCII and we attempt to log a non-ASCII string
Revision 1.24 / (download) - annotate - [select for diffs], Mon May 13 20:38:12 2019 UTC (4 years, 11 months ago) by adam
Branch: MAIN
Changes since 1.23: +2 -2
lines
Diff to previous 1.23 (colored) to selected 1.12 (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.23 / (download) - annotate - [select for diffs], Sun Feb 17 08:26:12 2019 UTC (5 years, 2 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2019Q1-base,
pkgsrc-2019Q1
Changes since 1.22: +2 -2
lines
Diff to previous 1.22 (colored) to selected 1.12 (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.22 / (download) - annotate - [select for diffs], Fri Nov 9 18:12:26 2018 UTC (5 years, 5 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q4-base,
pkgsrc-2018Q4
Changes since 1.21: +2 -2
lines
Diff to previous 1.21 (colored) to selected 1.12 (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.21 / (download) - annotate - [select for diffs], Fri Aug 10 11:56:09 2018 UTC (5 years, 8 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q3-base,
pkgsrc-2018Q3
Changes since 1.20: +2 -2
lines
Diff to previous 1.20 (colored) to selected 1.12 (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.20 / (download) - annotate - [select for diffs], Sun May 13 08:13:46 2018 UTC (5 years, 11 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q2-base,
pkgsrc-2018Q2
Changes since 1.19: +2 -2
lines
Diff to previous 1.19 (colored) to selected 1.12 (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.19 / (download) - annotate - [select for diffs], Fri Mar 2 17:11:11 2018 UTC (6 years, 1 month ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q1-base,
pkgsrc-2018Q1
Changes since 1.18: +2 -2
lines
Diff to previous 1.18 (colored) to selected 1.12 (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.18 / (download) - annotate - [select for diffs], Thu Feb 8 20:53:57 2018 UTC (6 years, 2 months ago) by adam
Branch: MAIN
Changes since 1.17: +2 -2
lines
Diff to previous 1.17 (colored) to selected 1.12 (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.17 / (download) - annotate - [select for diffs], Fri Dec 15 16:52:24 2017 UTC (6 years, 4 months ago) by dholland
Branch: MAIN
CVS Tags: pkgsrc-2017Q4-base,
pkgsrc-2017Q4
Changes since 1.16: +0 -2
lines
Diff to previous 1.16 (colored) to selected 1.12 (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.16 / (download) - annotate - [select for diffs], Thu Dec 7 14:19:32 2017 UTC (6 years, 4 months ago) by adam
Branch: MAIN
Changes since 1.15: +2 -1
lines
Diff to previous 1.15 (colored) to selected 1.12 (colored)
postgresql: removed obsolete "kerberos" option; fix for #52787
Revision 1.15 / (download) - annotate - [select for diffs], Mon Nov 13 09:35:46 2017 UTC (6 years, 5 months ago) by adam
Branch: MAIN
Changes since 1.14: +2 -1
lines
Diff to previous 1.14 (colored) to selected 1.12 (colored)
Brought back removed lines
Revision 1.14 / (download) - annotate - [select for diffs], Mon Nov 13 09:33:32 2017 UTC (6 years, 5 months ago) by adam
Branch: MAIN
Changes since 1.13: +14 -13
lines
Diff to previous 1.13 (colored) to selected 1.12 (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.13 / (download) - annotate - [select for diffs], Fri Nov 10 14:47:41 2017 UTC (6 years, 5 months ago) by fhajny
Branch: MAIN
Changes since 1.12: +9 -1
lines
Diff to previous 1.12 (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.9.2.1 / (download) - annotate - [select for diffs], Wed Sep 13 06:23:56 2017 UTC (6 years, 7 months ago) by spz
Branch: pkgsrc-2017Q2
Changes since 1.9: +2 -2
lines
Diff to previous 1.9 (colored) next main 1.10 (colored) to selected 1.12 (colored)
Pullup ticket #5540 - requested by taca
databases/postgresql95: security update
databases/postgresql95-client: security update
databases/postgresql95-docs: security update
databases/postgresql95-server: security update
Revisions pulled up:
- databases/postgresql95-client/Makefile 1.5
- databases/postgresql95-docs/PLIST 1.8
- databases/postgresql95/Makefile.common 1.10
- databases/postgresql95/distinfo 1.9
- databases/postgresql95/patches/patch-src_pl_plperl_plperl.h 1.2
-------------------------------------------------------------------
Module Name: pkgsrc
Committed By: adam
Date: Sun Aug 13 19:25:18 UTC 2017
Modified Files:
pkgsrc/databases/postgresql92: Makefile.common distinfo
pkgsrc/databases/postgresql92-docs: PLIST
pkgsrc/databases/postgresql92/patches: patch-src_pl_plperl_plperl.h
pkgsrc/databases/postgresql93: Makefile.common distinfo
pkgsrc/databases/postgresql93-docs: PLIST
pkgsrc/databases/postgresql93/patches: patch-src_pl_plperl_plperl.h
pkgsrc/databases/postgresql94: Makefile.common distinfo
pkgsrc/databases/postgresql94-docs: PLIST
pkgsrc/databases/postgresql94/patches: patch-src_pl_plperl_plperl.h
pkgsrc/databases/postgresql95: Makefile.common distinfo
pkgsrc/databases/postgresql95-client: Makefile
pkgsrc/databases/postgresql95-docs: PLIST
pkgsrc/databases/postgresql95/patches: patch-src_pl_plperl_plperl.h
pkgsrc/databases/postgresql96: Makefile.common distinfo
pkgsrc/databases/postgresql96-client: Makefile PLIST
pkgsrc/databases/postgresql96-docs: PLIST
pkgsrc/databases/postgresql96/patches: patch-src_pl_plperl_plperl.h
Log Message:
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.4, 9.5.8, 9.4.13, 9.3.18, and 9.2.22. This release fixes three security issues. It also patches over 50 other bugs reported over the last three months. Users who are affected by the below security issues should update as soon as possible. Users affected by CVE-2017-7547 will need to perform additional steps after upgrading to resolve the issue. Other users should plan to update at the next convenient downtime.
Three security vulnerabilities have been closed by this release:
* CVE-2017-7546: Empty password accepted in some authentication methods
* CVE-2017-7547: The "pg_user_mappings" catalog view discloses passwords to users lacking server privileges
* CVE-2017-7548: lo_put() function ignores ACLs
To generate a diff of this commit:
cvs rdiff -u -r1.9 -r1.10 pkgsrc/databases/postgresql95/Makefile.common
cvs rdiff -u -r1.8 -r1.9 pkgsrc/databases/postgresql95/distinfo
cvs rdiff -u -r1.4 -r1.5 pkgsrc/databases/postgresql95-client/Makefile
cvs rdiff -u -r1.7 -r1.8 pkgsrc/databases/postgresql95-docs/PLIST
cvs rdiff -u -r1.1 -r1.2 \
pkgsrc/databases/postgresql95/patches/patch-src_pl_plperl_plperl.h
Revision 1.12 / (download) - annotate - [selected], Mon Sep 4 19:33:43 2017 UTC (6 years, 7 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2017Q3-base,
pkgsrc-2017Q3
Changes since 1.11: +2 -2
lines
Diff to previous 1.11 (colored)
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.5, 9.5.9, 9.4.14, 9.3.19, and 9.2.23. This release includes fixes that prevent a crash in pg_restore when using parallel mode. It also patches over a few other bugs reported since the last releases in August. Additionally, in 9.4.14 only, there is a fix to an issue with walsenders preventing primary-server shutdown unless immediate shutdown mode is used. Users should plan to update at the next convenient downtime.
Revision 1.11 / (download) - annotate - [select for diffs], Sun Sep 3 08:53:06 2017 UTC (6 years, 7 months ago) by wiz
Branch: MAIN
Changes since 1.10: +2 -2
lines
Diff to previous 1.10 (colored) to selected 1.12 (colored)
Follow some redirects.
Revision 1.10 / (download) - annotate - [select for diffs], Sun Aug 13 19:25:17 2017 UTC (6 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.9: +2 -2
lines
Diff to previous 1.9 (colored) to selected 1.12 (colored)
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.4, 9.5.8, 9.4.13, 9.3.18, and 9.2.22. This release fixes three security issues. It also patches over 50 other bugs reported over the last three months. Users who are affected by the below security issues should update as soon as possible. Users affected by CVE-2017-7547 will need to perform additional steps after upgrading to resolve the issue. Other users should plan to update at the next convenient downtime. Three security vulnerabilities have been closed by this release: * CVE-2017-7546: Empty password accepted in some authentication methods * CVE-2017-7547: The "pg_user_mappings" catalog view discloses passwords to users lacking server privileges * CVE-2017-7548: lo_put() function ignores ACLs
Revision 1.8.2.1 / (download) - annotate - [select for diffs], Mon May 29 19:24:33 2017 UTC (6 years, 10 months ago) by bsiegert
Branch: pkgsrc-2017Q1
Changes since 1.8: +2 -2
lines
Diff to previous 1.8 (colored) next main 1.9 (colored) to selected 1.12 (colored)
Pullup ticket #5434 - requested by sevan
databases/postgresql92: security fix
databases/postgresql93: security fix
databases/postgresql94: security fix
databases/postgresql95: security fix
databases/postgresql96: security fix
Revisions pulled up:
- databases/postgresql92-docs/PLIST 1.21
- databases/postgresql92-server/PLIST 1.13
- databases/postgresql92/Makefile.common 1.28
- databases/postgresql92/distinfo 1.23
- databases/postgresql93-docs/PLIST 1.18
- databases/postgresql93-server/PLIST 1.11
- databases/postgresql93/Makefile.common 1.24
- databases/postgresql93/distinfo 1.23
- databases/postgresql94-client/PLIST 1.3
- databases/postgresql94-docs/PLIST 1.13
- databases/postgresql94-server/PLIST 1.8
- databases/postgresql94/Makefile.common 1.16
- databases/postgresql94/distinfo 1.15
- databases/postgresql95-client/PLIST 1.4
- databases/postgresql95-docs/PLIST 1.7
- databases/postgresql95-server/PLIST 1.6
- databases/postgresql95/Makefile.common 1.9
- databases/postgresql95/distinfo 1.8
- databases/postgresql96-client/PLIST 1.2
- databases/postgresql96-docs/PLIST 1.3
- databases/postgresql96-server/PLIST 1.3
- databases/postgresql96/Makefile.common 1.3
- databases/postgresql96/distinfo 1.4
---
Module Name: pkgsrc
Committed By: adam
Date: Fri May 12 19:37:55 UTC 2017
Modified Files:
pkgsrc/databases/postgresql92: Makefile.common distinfo
pkgsrc/databases/postgresql92-docs: PLIST
pkgsrc/databases/postgresql92-server: PLIST
pkgsrc/databases/postgresql93: Makefile.common distinfo
pkgsrc/databases/postgresql93-docs: PLIST
pkgsrc/databases/postgresql93-server: PLIST
pkgsrc/databases/postgresql94: Makefile.common distinfo
pkgsrc/databases/postgresql94-client: PLIST
pkgsrc/databases/postgresql94-docs: PLIST
pkgsrc/databases/postgresql94-server: PLIST
pkgsrc/databases/postgresql95: Makefile.common distinfo
pkgsrc/databases/postgresql95-client: PLIST
pkgsrc/databases/postgresql95-docs: PLIST
pkgsrc/databases/postgresql95-server: PLIST
pkgsrc/databases/postgresql96: Makefile.common distinfo
pkgsrc/databases/postgresql96-client: PLIST
pkgsrc/databases/postgresql96-docs: PLIST
pkgsrc/databases/postgresql96-server: PLIST
Log Message:
The PostgreSQL Global Development Group has released an update to all
supported versions of our database system, including 9.6.3, 9.5.7,
9.4.12, 9.3.17, and 9.2.21. This release fixes three security
issues. It also patches a number of other bugs reported over the last
three months. Users who use the PGREQUIRESSL environment variable to
control connections, and users who rely on security
isolation between database users when using foreign servers, should
update as soon as possible. Other users should plan to update at the
next convenient downtime.
Revision 1.9 / (download) - annotate - [select for diffs], Fri May 12 19:37:55 2017 UTC (6 years, 11 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2017Q2-base
Branch point for: pkgsrc-2017Q2
Changes since 1.8: +2 -2
lines
Diff to previous 1.8 (colored) to selected 1.12 (colored)
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.3, 9.5.7, 9.4.12, 9.3.17, and 9.2.21. This release fixes three security issues. It also patches a number of other bugs reported over the last three months. Users who use the PGREQUIRESSL environment variable to control connections, and users who rely on security isolation between database users when using foreign servers, should update as soon as possible. Other users should plan to update at the next convenient downtime.
Revision 1.8 / (download) - annotate - [select for diffs], Sat Feb 11 10:18:52 2017 UTC (7 years, 2 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2017Q1-base
Branch point for: pkgsrc-2017Q1
Changes since 1.7: +2 -2
lines
Diff to previous 1.7 (colored) to selected 1.12 (colored)
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.2, 9.5.6, 9.4.11, 9.3.16, and 9.2.20. This release includes fixes that prevent data corruption issues in index builds and in certain write-ahead-log replay situations, which are detailed below. It also patches over 75 other bugs reported over the last three months.
Revision 1.7 / (download) - annotate - [select for diffs], Sat Oct 29 19:41:54 2016 UTC (7 years, 5 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2016Q4-base,
pkgsrc-2016Q4
Changes since 1.6: +2 -2
lines
Diff to previous 1.6 (colored) to selected 1.12 (colored)
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.1, 9.5.5, 9.4.10, 9.3.15, 9.2.19, and 9.1.24. This is also the last update for the PostgreSQL 9.1 series as it is now end-of-life. This release fixes two issues that can cause data corruption, which are described in more detail below. It also patches a number of other bugs reported over the last three months. The project urges users to apply this update at the next possible downtime.
Revision 1.6 / (download) - annotate - [select for diffs], Tue Aug 23 06:28:16 2016 UTC (7 years, 7 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2016Q3-base,
pkgsrc-2016Q3
Changes since 1.5: +2 -2
lines
Diff to previous 1.5 (colored) to selected 1.12 (colored)
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
Revision 1.5 / (download) - annotate - [select for diffs], Sun Jun 19 21:09:57 2016 UTC (7 years, 9 months ago) by fhajny
Branch: MAIN
CVS Tags: pkgsrc-2016Q2-base,
pkgsrc-2016Q2
Changes since 1.4: +1 -9
lines
Diff to previous 1.4 (colored) to selected 1.12 (colored)
Remove PostgreSQL split-up contrib packages, now replaced by single postgresql9[1-5]-contrib packages. OK by adam@.
Revision 1.4 / (download) - annotate - [select for diffs], Sun Jun 19 20:48:29 2016 UTC (7 years, 9 months ago) by fhajny
Branch: MAIN
Changes since 1.3: +2 -1
lines
Diff to previous 1.3 (colored) to selected 1.12 (colored)
Import postgresql9[1-5]-contrib packages. These supersede the previous handful of packages like -datatypes or -dblink. They contain all of the contrib subtree, matching what similar packages carry in e.g. FreeBSD ports or what PostgreSQL users generally expect. This subtree contains porting tools, analysis utilities, and plug-in features that are not part of the core PostgreSQL system, mainly because they address a limited audience or are too experimental to be part of the main source tree. This does not preclude their usefulness.
Revision 1.3 / (download) - annotate - [select for diffs], Mon May 23 14:27:35 2016 UTC (7 years, 10 months ago) by adam
Branch: MAIN
Changes since 1.2: +2 -2
lines
Diff to previous 1.2 (colored) to selected 1.12 (colored)
This release fixes a number of issues reported by users over the last two months. Most database administrators should plan to upgrade at the next available downtime, unless they have been affected directly by the fixed issues.
Revision 1.1.2.1 / (download) - annotate - [select for diffs], Wed Apr 27 20:12:36 2016 UTC (7 years, 11 months ago) by bsiegert
Branch: pkgsrc-2016Q1
Changes since 1.1: +2 -2
lines
Diff to previous 1.1 (colored) next main 1.2 (colored) to selected 1.12 (colored)
Pullup ticket #4964 - requested by sevan
databases/postgresql95: security fix
Revisions pulled up:
- databases/postgresql95-adminpack/Makefile 1.3
- databases/postgresql95-client/Makefile 1.3
- databases/postgresql95-client/PLIST 1.2
- databases/postgresql95-datatypes/Makefile 1.3
- databases/postgresql95-dblink/Makefile 1.3
- databases/postgresql95-docs/PLIST 1.2
- databases/postgresql95-fuzzystrmatch/Makefile 1.3
- databases/postgresql95-monitoring/Makefile 1.3
- databases/postgresql95-pgcrypto/Makefile 1.3
- databases/postgresql95-plperl/Makefile 1.3
- databases/postgresql95-plpython/Makefile 1.3
- databases/postgresql95-pltcl/Makefile 1.3
- databases/postgresql95-replicationtools/Makefile 1.3
- databases/postgresql95-server/Makefile 1.4
- databases/postgresql95-server/PLIST 1.2
- databases/postgresql95/Makefile 1.3
- databases/postgresql95/Makefile.common 1.2
- databases/postgresql95/distinfo 1.2
---
Module Name: pkgsrc
Committed By: adam
Date: Sat Apr 9 12:51:50 UTC 2016
Modified Files:
pkgsrc/databases/postgresql91: Makefile Makefile.common distinfo
pkgsrc/databases/postgresql91-adminpack: Makefile
pkgsrc/databases/postgresql91-client: Makefile
pkgsrc/databases/postgresql91-datatypes: Makefile
pkgsrc/databases/postgresql91-dblink: Makefile
pkgsrc/databases/postgresql91-docs: PLIST
pkgsrc/databases/postgresql91-fuzzystrmatch: Makefile
pkgsrc/databases/postgresql91-monitoring: Makefile
pkgsrc/databases/postgresql91-pgcrypto: Makefile
pkgsrc/databases/postgresql91-plperl: Makefile
pkgsrc/databases/postgresql91-plpython: Makefile
pkgsrc/databases/postgresql91-pltcl: Makefile
pkgsrc/databases/postgresql91-replicationtools: Makefile
pkgsrc/databases/postgresql91-server: Makefile PLIST
pkgsrc/databases/postgresql91-upgrade: Makefile
pkgsrc/databases/postgresql92: Makefile Makefile.common distinfo
pkgsrc/databases/postgresql92-adminpack: Makefile
pkgsrc/databases/postgresql92-client: Makefile
pkgsrc/databases/postgresql92-datatypes: Makefile
pkgsrc/databases/postgresql92-dblink: Makefile
pkgsrc/databases/postgresql92-docs: PLIST
pkgsrc/databases/postgresql92-fuzzystrmatch: Makefile
pkgsrc/databases/postgresql92-monitoring: Makefile
pkgsrc/databases/postgresql92-pgcrypto: Makefile
pkgsrc/databases/postgresql92-plperl: Makefile
pkgsrc/databases/postgresql92-plpython: Makefile
pkgsrc/databases/postgresql92-pltcl: Makefile
pkgsrc/databases/postgresql92-replicationtools: Makefile
pkgsrc/databases/postgresql92-server: Makefile PLIST
pkgsrc/databases/postgresql92-upgrade: Makefile
pkgsrc/databases/postgresql93: Makefile Makefile.common distinfo
pkgsrc/databases/postgresql93-adminpack: Makefile
pkgsrc/databases/postgresql93-client: Makefile
pkgsrc/databases/postgresql93-datatypes: Makefile
pkgsrc/databases/postgresql93-dblink: Makefile
pkgsrc/databases/postgresql93-docs: PLIST
pkgsrc/databases/postgresql93-fuzzystrmatch: Makefile
pkgsrc/databases/postgresql93-monitoring: Makefile
pkgsrc/databases/postgresql93-pgcrypto: Makefile
pkgsrc/databases/postgresql93-plperl: Makefile
pkgsrc/databases/postgresql93-plpython: Makefile
pkgsrc/databases/postgresql93-pltcl: Makefile
pkgsrc/databases/postgresql93-replicationtools: Makefile
pkgsrc/databases/postgresql93-server: Makefile PLIST
pkgsrc/databases/postgresql93-upgrade: Makefile
pkgsrc/databases/postgresql94: Makefile Makefile.common distinfo
pkgsrc/databases/postgresql94-adminpack: Makefile
pkgsrc/databases/postgresql94-client: Makefile
pkgsrc/databases/postgresql94-datatypes: Makefile
pkgsrc/databases/postgresql94-dblink: Makefile
pkgsrc/databases/postgresql94-docs: PLIST
pkgsrc/databases/postgresql94-fuzzystrmatch: Makefile
pkgsrc/databases/postgresql94-monitoring: Makefile
pkgsrc/databases/postgresql94-pgcrypto: Makefile
pkgsrc/databases/postgresql94-plperl: Makefile
pkgsrc/databases/postgresql94-plpython: Makefile
pkgsrc/databases/postgresql94-pltcl: Makefile
pkgsrc/databases/postgresql94-replicationtools: Makefile
pkgsrc/databases/postgresql94-server: Makefile PLIST
pkgsrc/databases/postgresql94-upgrade: Makefile
pkgsrc/databases/postgresql95: Makefile Makefile.common distinfo
pkgsrc/databases/postgresql95-adminpack: Makefile
pkgsrc/databases/postgresql95-client: Makefile PLIST
pkgsrc/databases/postgresql95-datatypes: Makefile
pkgsrc/databases/postgresql95-dblink: Makefile
pkgsrc/databases/postgresql95-docs: PLIST
pkgsrc/databases/postgresql95-fuzzystrmatch: Makefile
pkgsrc/databases/postgresql95-monitoring: Makefile
pkgsrc/databases/postgresql95-pgcrypto: Makefile
pkgsrc/databases/postgresql95-plperl: Makefile
pkgsrc/databases/postgresql95-plpython: Makefile
pkgsrc/databases/postgresql95-pltcl: Makefile
pkgsrc/databases/postgresql95-replicationtools: Makefile
pkgsrc/databases/postgresql95-server: Makefile PLIST
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.
Revision 1.2 / (download) - annotate - [select for diffs], Sat Apr 9 12:51:49 2016 UTC (8 years ago) by adam
Branch: MAIN
Changes since 1.1: +2 -2
lines
Diff to previous 1.1 (colored) to selected 1.12 (colored)
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.
Revision 1.1 / (download) - annotate - [select for diffs], Thu Feb 25 21:37:35 2016 UTC (8 years, 1 month ago) by tnn
Branch: MAIN
CVS Tags: pkgsrc-2016Q1-base
Branch point for: pkgsrc-2016Q1
Diff to selected 1.12 (colored)
Add postgresql95 packages, converted from corresponding postgresql94
packages. postgresql95-upgrade is gone, the pg_upgrade tool is shipped
with postgresql95-client now.
Major enhancements in PostgreSQL 9.5 include:
Allow INSERTs that would generate constraint conflicts to be turned into
UPDATEs or ignored
Add GROUP BY analysis features GROUPING SETS, CUBE and ROLLUP
Add row-level security control
Create mechanisms for tracking the progress of replication, including
methods for identifying the origin of individual changes during logical
replication
Add Block Range Indexes (BRIN)
Substantial performance improvements for sorting
Substantial performance improvements for multi-CPU machines