The NetBSD Project

CVS log for pkgsrc/databases/postgresql12-server/Attic/PLIST

[BACK] Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql12-server

Request diff between arbitrary revisions


Keyword substitution: kv
Default branch: MAIN


Revision 1.9
Sat Nov 16 10:13:47 2024 UTC (23 months, 4 weeks ago) by adam
Branches: MAIN
CVS tags: HEAD
FILE REMOVED
Changes since revision 1.8: +1 -1 lines
postgresql: updated to 17.1, 16.5, 15.9, 14.14, 13.17

PostgreSQL 12 is now end-of-life.

Security Issues
* CVE-2024-10976: PostgreSQL row security below e.g. subqueries disregards user ID changes
* CVE-2024-10977: PostgreSQL libpq retains an error message from man-in-the-middle
* CVE-2024-10978: PostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong user ID
* CVE-2024-10979: PostgreSQL PL/Perl environment variable changes execute arbitrary code

Bug Fixes and Improvements

This update fixes over 35 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 17. Some of these issues may also affect other supported versions of PostgreSQL.

Fix when attaching or detaching table partitions with foreign key constraints. After upgrade, users impacted by this issue will need to perform manual steps to finish fixing it. Please see the "Upgrading" section and the release notes for more information.
Fix when using libc as the default collation provider when LC_CTYPE is C while LC_COLLATE is a different locale. This could lead to incorrect query results. If you have these settings in your database, please reindex any affected indexes after updating to this release. This issue impacted 17.0 only.
Several query planner fixes, including disallowing joining partitions (partitionwise join) if the collations of the partitions don't match.
Fix possible wrong answers or wrong varnullingrels planner errors for MERGE ... WHEN NOT MATCHED BY SOURCE actions.
Fix validation of the COPY FORCE_NOT_NULL and FORCE_NULL.
Fix server crash when a json_objectagg() call contains a volatile function.
Ensure there's a registered dependency between a partitioned table and a non-built-in access method specified in CREATE TABLE ... USING. This fix only prevents problems for partitioned tables created after this update.
Fix race condition in committing a serializable transaction.
Fix race condition in COMMIT PREPARED that could require manual file removal after a crash-and-recovery.
Fix for pg_cursors view to prevent errors by excluding cursors that aren't completely set up.
Reduce logical decoding memory consumption.
Fix to prevent stable functions from receiving stale row values when they're called from a CALL statement's argument list and the CALL is within a PL/pgSQL EXCEPTION block.
Fix for JIT crashes on ARM (aarch64) systems.
The psql \watch now treats values that are less than 1ms to be 0 (no wait between executions).
Fix failure to use credentials for a replication user in the password file (pgpass)
pg_combinebackup now throws an error if an incremental backup file is present in a directory that should contain a full backup.
Fix to avoid reindexing temporary tables and indexes in vacuumdb and parallel reindexdb

Revision 1.8: download - view: text, markup, annotated - select for diffs
Wed Feb 15 20:50:58 2023 UTC (3 years, 9 months ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2024Q3-base, pkgsrc-2024Q3, pkgsrc-2024Q2-base, pkgsrc-2024Q2, pkgsrc-2024Q1-base, pkgsrc-2024Q1, pkgsrc-2023Q4-base, pkgsrc-2023Q4, pkgsrc-2023Q3-base, pkgsrc-2023Q3, pkgsrc-2023Q2-base, pkgsrc-2023Q2, pkgsrc-2023Q1-base, pkgsrc-2023Q1
Diff to: previous 1.7: preferred, colored
Changes since revision 1.7: +2 -1 lines
postgresql: updated to 15.2, 14.7, 13.10, 12.14, and 11.19

Security Issues

CVE-2022-41862: Client memory disclosure when connecting, with Kerberos, to modified server.

Versions Affected: 12 - 15.

A modified, unauthenticated server or an unauthenticated man-in-the-middle can send an unterminated string during the establishment of Kerberos transport encryption. When a libpq client application has a Kerberos credential cache and doesn't explicitly disable option gssencmode, a server can cause libpq to over-read and report an error message containing uninitialized bytes from and following its receive buffer. If libpq's caller somehow makes that message accessible to the attacker, this achieves a disclosure of the over-read bytes. We have not confirmed or ruled out viability of attacks that arrange for a crash or for presence of notable, confidential information in disclosed bytes.

The PostgreSQL project thanks Jacob Champion for reporting this problem.

Bug Fixes and Improvements

This update fixes over 60 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 15. Some of these issues may also affect other supported versions of PostgreSQL.

Included in this release:

Fix for partitioned tables to correctly update GENERATED columns in child tables if the GENERATED column does not exist in the parent table or the child generated column has different dependencies than the parent.
Several fixes for the MERGE command.
Allow a WITH RECURSIVE ... CYCLE query to access its SET output column.
Fix an issue with bulk insertions on foreign tables that could lead to logical inconsistencies, for example, a BEFORE ROW trigger may not process rows that should be available.
Reject uses of undefined variables in jsonpath existence checks.
Fix for jsonb subscripting that come directly from a text column in a table.
Honor updated values of checkpoint_completion_target on reload.
Log the correct ending timestamp in recovery_target_xid mode.
Fix issue to allow column lists longer than 100 when using logical replication.
Prevent "wrong tuple length" failure at the end of VACUUM.
Avoid an immediate commit after ANALYZE when using query pipelining.
Several fixes to the query planner, including one that provides more opportunities for using memoization with partitionwise joins.
Fix for statistics collection to correctly handle when a relation changes type (e.g. a table is converted to a view).
Ensure full text search queries can be cancelled while performing phrase matches.
Fix deadlock between DROP DATABASE and logical replication worker process.
Fix small session-lifespan memory leak when CREATE SUBSCRIPTION fails its connection attempt.
Performance improvement for replicas with hot_standby enabled that are processing SELECT queries.
Several fixes for logical decoding that improve its stability and bloat handling.
Fix the default logical replication plug-in, pgoutput, to not send columns that are not listed in a table's replication column list.
Fix possible corruption of very large tablespace map files in pg_basebackup.
Remove a harmless warning from pg_dump in --if-exists mode when the public schema has a non-default owner.
Fix the psql commands \sf and \ef to handle SQL-language functions that have SQL-standard function bodies (i.e. BEGIN ATOMIC).
Fix tab completion of ALTER FUNCTION/PROCEDURE/ROUTINE ... SET SCHEMA.
Update the pageinspect extension to mark its disk-accessing functions as PARALLEL RESTRICTED.
Fix the seg extension to not crash or print garbage if an input number has more than 127 digits.

Revision 1.7: download - view: text, markup, annotated - select for diffs
Sun Nov 13 09:34:26 2022 UTC (4 years ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2022Q4-base, pkgsrc-2022Q4
Diff to: previous 1.6: preferred, colored
Changes since revision 1.6: +2 -1 lines
postgresql1[0-5]: Updated to 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23

PostgreSQL 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23 Released!

Bug Fixes and Improvements

This update fixes over 25 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 15. Some of these issues may also affect other supported versions of PostgreSQL.

Included in this release:

Fix for updatable views for INSERT statements that include multi-row VALUES clauses with a DEFAULT set.
Disallow rules named _RETURN that are not ON SELECT rules.
Disallow use of MERGE on a partitioned table that has foreign-table partitions.
Fix for construction of per-partition foreign key constraints while doing ALTER TABLE ... ATTACH PARTITION, where previously incorrect or duplicate constraints could be built.
Fix for a planner failure with extended statistics on partitioned or inherited tables.
Fix bugs in logical decoding that could lead to memory leaks when replay starts from a point between the beginning of a transaction and the beginning of its subtransaction.
Fix issues with slow shutdown of replication workers by allowing interrupts in more places.
Disallow logical replication into foreign-table partitions.
Prevent crash in replication works after a SQL or PL/pgSQL function syntax error.
psql -c now exits with a nonzero status if the query is canceled.
Allow cross-platform tablespace relocation in pg_basebackup.
Fix pg_dump to include comments attached to some CHECK constraints.

Revision 1.5.10.1: download - view: text, markup, annotated - select for diffs
Wed Nov 24 14:31:20 2021 UTC (4 years, 11 months ago) by tm
Branches: pkgsrc-2021Q3
Diff to: previous 1.5: preferred, colored; next MAIN 1.6: preferred, colored
Changes since revision 1.5: +2 -1 lines
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

Revision 1.6: download - view: text, markup, annotated - select for diffs
Tue Nov 16 10:14:37 2021 UTC (5 years ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2022Q3-base, pkgsrc-2022Q3, pkgsrc-2022Q2-base, pkgsrc-2022Q2, pkgsrc-2022Q1-base, pkgsrc-2022Q1, pkgsrc-2021Q4-base, pkgsrc-2021Q4
Diff to: previous 1.5: preferred, colored
Changes since revision 1.5: +2 -1 lines
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.

Revision 1.5: download - view: text, markup, annotated - select for diffs
Fri Aug 14 06:56:24 2020 UTC (6 years, 3 months ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2021Q3-base, pkgsrc-2021Q2-base, pkgsrc-2021Q2, pkgsrc-2021Q1-base, pkgsrc-2021Q1, pkgsrc-2020Q4-base, pkgsrc-2020Q4, pkgsrc-2020Q3-base, pkgsrc-2020Q3
Branch point for: pkgsrc-2021Q3
Diff to: previous 1.4: preferred, colored
Changes since revision 1.4: +2 -1 lines
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.4: download - view: text, markup, annotated - select for diffs
Fri May 15 09:45:01 2020 UTC (6 years, 6 months ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2020Q2-base, pkgsrc-2020Q2
Diff to: previous 1.3: preferred, colored
Changes since revision 1.3: +2 -1 lines
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.3: download - view: text, markup, annotated - select for diffs
Thu Nov 28 19:37:41 2019 UTC (6 years, 11 months ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2020Q1-base, pkgsrc-2020Q1, pkgsrc-2019Q4-base, pkgsrc-2019Q4
Diff to: previous 1.2: preferred, colored
Changes since revision 1.2: +24 -7 lines
postgresql12-server: PLIST fix for LLVM option

Revision 1.2: download - view: text, markup, annotated - select for diffs
Thu Oct 24 07:57:14 2019 UTC (7 years ago) by triaxx
Branches: MAIN
Diff to: previous 1.1: preferred, colored
Changes since revision 1.1: +27 -27 lines
postgresql12: make nls support optional

Revision 1.1: download - view: text, markup, annotated - select for diffs
Mon Oct 7 19:21:49 2019 UTC (7 years, 1 month ago) by adam
Branches: MAIN
postgresql12: added version 12.0

Release 12:

General performance improvements, including:
* Optimizations to space utilization and read/write performance for B-tree indexes
* Partitioning performance enhancements, including improved query performance on tables with thousands of partitions, improved insertion performance with INSERT and COPY, and the ability to execute ALTER TABLE ATTACH PARTITION without blocking queries
* Automatic (but overridable) inlining of common table expressions (CTEs)
* Reduction of WAL overhead for creation of GiST, GIN, and SP-GiST indexes
* Support for covering GiST indexes, via the INCLUDE clause
* Multi-column most-common-value (MCV) statistics can be defined via CREATE STATISTICS, to support better plans for queries that test several non-uniformly-distributed columns

Enhancements to administrative functionality, including:
* REINDEX CONCURRENTLY can rebuild an index without blocking writes to its table
* pg_checksums can enable/disable page checksums (used for detecting data corruption) in an offline cluster
* Progress reporting statistics for CREATE INDEX, REINDEX, CLUSTER, VACUUM FULL, and pg_checksums

Support for the SQL/JSON path language

Stored generated columns

Nondeterministic ICU collations, enabling case-insensitive and accent-insensitive grouping and ordering

New authentication features, including:
* Encryption of TCP/IP connections when using GSSAPI authentication
* Discovery of LDAP servers using DNS SRV records
* Multi-factor authentication, using the clientcert=verify-full option combined with an additional authentication method in pg_hba.conf

Diff request

This form allows you to request diffs between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.

Log view options

CVSweb <webmaster@jp.NetBSD.org>