Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql96-server
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
retire postgresql96 (EOL)
Pullup ticket #6535 - requested by bsiegert
databases/postgresql: security fix
Revisions pulled up:
- databases/postgresql10-docs/PLIST 1.20
- databases/postgresql10-server/PLIST 1.10
- databases/postgresql10/Makefile 1.27
- databases/postgresql10/Makefile.common 1.31
- databases/postgresql10/distinfo 1.25
- databases/postgresql11-docs/PLIST 1.15
- databases/postgresql11-server/PLIST 1.5
- databases/postgresql11/Makefile.common 1.24
- databases/postgresql11/distinfo 1.20
- databases/postgresql12-docs/PLIST 1.10
- databases/postgresql12-server/PLIST 1.6
- databases/postgresql12/Makefile 1.18
- databases/postgresql12/Makefile.common 1.17
- databases/postgresql12/distinfo 1.14
- databases/postgresql13-client/PLIST 1.5
- databases/postgresql13-docs/PLIST 1.6
- databases/postgresql13-server/PLIST 1.4
- databases/postgresql13/Makefile 1.9
- databases/postgresql13/Makefile.common 1.10
- databases/postgresql13/distinfo 1.10
- databases/postgresql96-docs/PLIST 1.24
- databases/postgresql96-server/PLIST 1.9
- databases/postgresql96/Makefile 1.16
- databases/postgresql96/Makefile.common 1.36
- databases/postgresql96/distinfo 1.29
---
Module Name: pkgsrc
Committed By: adam
Date: Tue Nov 16 10:14:39 UTC 2021
Modified Files:
pkgsrc/databases/postgresql10: Makefile.common distinfo
pkgsrc/databases/postgresql10-docs: PLIST
pkgsrc/databases/postgresql10-server: PLIST
pkgsrc/databases/postgresql11: Makefile.common distinfo
pkgsrc/databases/postgresql11-docs: PLIST
pkgsrc/databases/postgresql11-server: PLIST
pkgsrc/databases/postgresql12: Makefile.common distinfo
pkgsrc/databases/postgresql12-docs: PLIST
pkgsrc/databases/postgresql12-server: PLIST
pkgsrc/databases/postgresql13: Makefile.common distinfo
pkgsrc/databases/postgresql13-client: PLIST
pkgsrc/databases/postgresql13-docs: PLIST
pkgsrc/databases/postgresql13-server: PLIST
pkgsrc/databases/postgresql96: Makefile.common distinfo
pkgsrc/databases/postgresql96-docs: PLIST
pkgsrc/databases/postgresql96-server: PLIST
Log Message:
postgresql: updated to 13.5, 12.9, 11.14, 10.19, 9.6.24
PostgreSQL 13.5, 12.9, 11.14, 10.19, and 9.6.24
Security Issues
CVE-2021-23214: Server processes unencrypted bytes from man-in-the-middle
Versions Affected: 9.6 - 14. The security team typically does not test
unsupported versions, but this problem is quite old.
When the server is configured to use trust authentication with a
clientcert requirement or to use cert authentication, a
man-in-the-middle attacker can inject arbitrary SQL queries when a
connection is first established, despite the use of SSL certificate
verification and encryption.
The PostgreSQL project thanks Jacob Champion for reporting this problem.
CVE-2021-23222: libpq processes unencrypted bytes from man-in-the-middle
Versions Affected: 9.6 - 14. The security team typically does not test
unsupported versions, but this problem is quite old.
A man-in-the-middle attacker can inject false responses to the
client's first few queries, despite the use of SSL certificate
verification and encryption.
If more preconditions hold, the attacker can exfiltrate the client's
password or other confidential data that might be transmitted early in
a session. The attacker must have a way to trick the client's intended
server into making the confidential data accessible to the attacker. A
known implementation having that property is a PostgreSQL
configuration vulnerable to CVE-2021-23214.
As with any exploitation of CVE-2021-23214, the server must be using
trust authentication with a clientcert requirement or using cert
authentication. To disclose a password, the client must be in
possession of a password, which is atypical when using an
authentication configuration vulnerable to CVE-2021-23214. The
attacker must have some other way to access the server to retrieve the
exfiltrated data (a valid, unprivileged login account would be
sufficient).
The PostgreSQL project thanks Jacob Champion for reporting this problem.
Bug Fixes and Improvements
This update fixes over 40 bugs that were reported in the last several
months. The issues listed below affect PostgreSQL 14. Some of these
issues may also affect other supported versions of PostgreSQL.
Some of these fixes include:
Fix physical replication for cases where the primary crashes after
shipping a WAL segment that ends with a partial WAL record. When
applying this update, update your standby servers before the primary
so that they will be ready to handle the fix if the primary happens to
crash.
Fix parallel VACUUM so that it will process indexes below the
min_parallel_index_scan_size threshold if the table has at least two
indexes that are above that size. This problem does not affect
autovacuum. If you are affected by this issue, you should reindex any
manually-vacuumed tables.
Fix causes of CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY
writing corrupt indexes. You should reindex any concurrently-built
indexes.
Fix for attaching/detaching a partition that could allow certain
INSERT/UPDATE queries to misbehave in active sessions.
Fix for creating a new range type with CREATE TYPE that could cause
problems for later event triggers or subsequent executions of the
CREATE TYPE command.
Fix updates of element fields in arrays of a domain that is a part of
a composite.
Disallow the combination of FETCH FIRST WITH TIES and FOR UPDATE SKIP LOCKED.
Fix corner-case loss of precision in the numeric power() function.
Fix restoration of a Portal's snapshot inside a subtransaction, which
could lead to a crash. For example, this could occur in PL/pgSQL when
a COMMIT is immediately followed by a BEGIN ... EXCEPTION block that
performs a query.
Clean up correctly if a transaction fails after exporting its
snapshot. This could occur if a replication slot was created then
rolled back, and then another replication slot was created in the same
session.
Fix for "overflowed-subtransaction" wraparound tracking on standby
servers that could lead to performance degradation.
Ensure that prepared transactions are properly accounted for during
promotion of a standby server.
Ensure that the correct lock level is used when renaming a table.
Avoid crash when dropping a role that owns objects being dropped concurrently.
Disallow setting huge_pages to on when shared_memory_type is sysv
Fix query type checking in the PL/pgSQL RETURN QUERY.
Several fixes for pg_dump, including the ability to dump non-global
default privileges correctly.
Use the CLDR project's data to map Windows time zone names to IANA time zones.
This update also contains tzdata release 2021e for DST law changes in
Fiji, Jordan, Palestine, and Samoa, plus historical corrections for
Barbados, Cook Islands, Guyana, Niue, Portugal, and Tonga.
Also, the Pacific/Enderbury zone has been renamed to Pacific/Kanton.
Also, the following zones have been merged into nearby, more-populous
zones whose clocks have agreed with them since 1970: Africa/Accra,
America/Atikokan, America/Blanc-Sablon, America/Creston,
America/Curacao, America/Nassau, America/Port_of_Spain,
Antarctica/DumontDUrville, and Antarctica/Syowa. In all these cases,
the previous zone name remains as an alias.
---
Module Name: pkgsrc
Committed By: adam
Date: Tue Nov 16 10:17:40 UTC 2021
Modified Files:
pkgsrc/databases/postgresql10: Makefile
pkgsrc/databases/postgresql12: Makefile
pkgsrc/databases/postgresql13: Makefile
pkgsrc/databases/postgresql96: Makefile
Log Message:
postgresqlNN: reset revision
postgresql: updated to 14.1, 13.5, 12.9, 11.14, 10.19, 9.6.24 PostgreSQL 14.1, 13.5, 12.9, 11.14, 10.19, and 9.6.24 Security Issues CVE-2021-23214: Server processes unencrypted bytes from man-in-the-middle Versions Affected: 9.6 - 14. The security team typically does not test unsupported versions, but this problem is quite old. When the server is configured to use trust authentication with a clientcert requirement or to use cert authentication, a man-in-the-middle attacker can inject arbitrary SQL queries when a connection is first established, despite the use of SSL certificate verification and encryption. The PostgreSQL project thanks Jacob Champion for reporting this problem. CVE-2021-23222: libpq processes unencrypted bytes from man-in-the-middle Versions Affected: 9.6 - 14. The security team typically does not test unsupported versions, but this problem is quite old. A man-in-the-middle attacker can inject false responses to the client's first few queries, despite the use of SSL certificate verification and encryption. If more preconditions hold, the attacker can exfiltrate the client's password or other confidential data that might be transmitted early in a session. The attacker must have a way to trick the client's intended server into making the confidential data accessible to the attacker. A known implementation having that property is a PostgreSQL configuration vulnerable to CVE-2021-23214. As with any exploitation of CVE-2021-23214, the server must be using trust authentication with a clientcert requirement or using cert authentication. To disclose a password, the client must be in possession of a password, which is atypical when using an authentication configuration vulnerable to CVE-2021-23214. The attacker must have some other way to access the server to retrieve the exfiltrated data (a valid, unprivileged login account would be sufficient). The PostgreSQL project thanks Jacob Champion for reporting this problem. Bug Fixes and Improvements This update fixes over 40 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 14. Some of these issues may also affect other supported versions of PostgreSQL. Some of these fixes include: Fix physical replication for cases where the primary crashes after shipping a WAL segment that ends with a partial WAL record. When applying this update, update your standby servers before the primary so that they will be ready to handle the fix if the primary happens to crash. Fix parallel VACUUM so that it will process indexes below the min_parallel_index_scan_size threshold if the table has at least two indexes that are above that size. This problem does not affect autovacuum. If you are affected by this issue, you should reindex any manually-vacuumed tables. Fix causes of CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY writing corrupt indexes. You should reindex any concurrently-built indexes. Fix for attaching/detaching a partition that could allow certain INSERT/UPDATE queries to misbehave in active sessions. Fix for creating a new range type with CREATE TYPE that could cause problems for later event triggers or subsequent executions of the CREATE TYPE command. Fix updates of element fields in arrays of a domain that is a part of a composite. Disallow the combination of FETCH FIRST WITH TIES and FOR UPDATE SKIP LOCKED. Fix corner-case loss of precision in the numeric power() function. Fix restoration of a Portal's snapshot inside a subtransaction, which could lead to a crash. For example, this could occur in PL/pgSQL when a COMMIT is immediately followed by a BEGIN ... EXCEPTION block that performs a query. Clean up correctly if a transaction fails after exporting its snapshot. This could occur if a replication slot was created then rolled back, and then another replication slot was created in the same session. Fix for "overflowed-subtransaction" wraparound tracking on standby servers that could lead to performance degradation. Ensure that prepared transactions are properly accounted for during promotion of a standby server. Ensure that the correct lock level is used when renaming a table. Avoid crash when dropping a role that owns objects being dropped concurrently. Disallow setting huge_pages to on when shared_memory_type is sysv Fix query type checking in the PL/pgSQL RETURN QUERY. Several fixes for pg_dump, including the ability to dump non-global default privileges correctly. Use the CLDR project's data to map Windows time zone names to IANA time zones. This update also contains tzdata release 2021e for DST law changes in Fiji, Jordan, Palestine, and Samoa, plus historical corrections for Barbados, Cook Islands, Guyana, Niue, Portugal, and Tonga. Also, the Pacific/Enderbury zone has been renamed to Pacific/Kanton. Also, the following zones have been merged into nearby, more-populous zones whose clocks have agreed with them since 1970: Africa/Accra, America/Atikokan, America/Blanc-Sablon, America/Creston, America/Curacao, America/Nassau, America/Port_of_Spain, Antarctica/DumontDUrville, and Antarctica/Syowa. In all these cases, the previous zone name remains as an alias.
missing PLIST updates
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
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
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
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 “work 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.
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.
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.
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.
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.