Re: 2022-02-10 release announcement draft
On 2/6/22 10:20 PM, Justin Pryzby wrote: On Sun, Feb 06, 2022 at 08:01:02PM -0500, Jonathan S. Katz wrote: Hi, Attached is a draft for the release announcement for the 2022-02-10 cumulative update release. Please review for technical accuracy or if you believe any items should be added/removed. Please provide feedback no later than 2020-02-10 0:00 AoE[1]. I guess you mean 2022 ;) Maybe ;) * The [`psql`](https://www.postgresql.org/docs/current/app-psql.html) `\password` command now defaults to setting the password for to the role defined by `CURRENT_USER`. Additionally, the role name is now included in the password prompt. s/for to/for/ Done. * Build extended statistics for partitioned tables. If you previously added extended statistics to a partitioned table, you can fix this by running [`ANALYZE`](https://www.postgresql.org/docs/current/sql-analyze.html). [`autovacuum`](https://www.postgresql.org/docs/current/routine-vacuuming.html#AUTOVACUUM) currently does not process these statistics, so you must periodically run `ANALYZE` on any partitioned tables that are using extended statistics. Instead of "you can fix this" , I suggest to say "you should run ANALYZE on those tables to collect updated statistics." I opted for most of this suggestion. It should say "not process these TABLES" (not stats), and should not say "that are using extended statistics" since partitioned tables should be manually analyzed whether or not they have extended stats. It's good to say "..you should periodically run ANALYZE on partitioned tables to collect updated statistics." (even though this patch doesn't change that). I reread the release note an agree, I misinterpreted this. I updated the language. * Fix crash with [multiranges](https://www.postgresql.org/docs/current/rangetypes.html) when extracting a variable-length data types. remove "a" or s/types/types/ Fixed. * Disallow altering data type of a partitioned table's columns when the partitioned table's row type is used as a composite type elsewhere. the data types ? This is correct, per 7ead9925f I've attached the updated copy. Thanks! Jonathan The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 14.2, 13.6, 12.10, 11.15, and 10.20. This release fixes over 55 bugs reported over the last three months. For the full list of changes, please review the [release notes](https://www.postgresql.org/docs/release/). Bug Fixes and Improvements -- This update fixes over 55 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. Included in this release: * Fix for a low probability scenario of index corruption when a HOT ([heap-only tuple](https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/access/heap/README.HOT;hb=HEAD)) chain changes state during `VACUUM`. Encountering this issue is unlikely, but if you are concerned, please consider [reindexing](https://www.postgresql.org/docs/current/sql-reindex.html). * Fix for using [`REINDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-reindex.html) on [TOAST](https://www.postgresql.org/docs/current/storage-toast.html) table indexes to prevent corruption. You can fix any TOAST indexes by [reindexing](https://www.postgresql.org/docs/current/sql-reindex.html) them again. * The [`psql`](https://www.postgresql.org/docs/current/app-psql.html) `\password` command now defaults to setting the password for the role defined by `CURRENT_USER`. Additionally, the role name is now included in the password prompt. * Build extended statistics for partitioned tables. If you previously added extended statistics to a partitioned table, you should run [`ANALYZE`](https://www.postgresql.org/docs/current/sql-analyze.html) on those tables. As [`autovacuum`](https://www.postgresql.org/docs/current/routine-vacuuming.html#AUTOVACUUM) currently does not process partitioned tables, you must periodically run `ANALYZE` on any partitioned tables to update their statistics. * Fix crash with [`ALTER STATISTICS`](https://www.postgresql.org/docs/current/sql-alterstatistics.html) when the statistics object is dropped concurrently. * Fix crash with [multiranges](https://www.postgresql.org/docs/current/rangetypes.html) when extracting variable-length data types. * Several fixes to the query planner that lead to incorrect query results. * Several fixes for query plan [memoization](https://www.postgresql.org/docs/current/runtime-config-query.html#GUC-ENABLE-MEMOIZE). * Fix startup of a physical replica to tolerate transaction ID wraparound. * When using logical replication, avoid duplicate transmission of a partitioned table's data when the publication includes both the child and parent tables. * Disallow altering data type of a partitioned table's columns when the partitioned table's row type
Re: 2022-02-10 release announcement draft
On Sun, Feb 06, 2022 at 08:01:02PM -0500, Jonathan S. Katz wrote: > Hi, > > Attached is a draft for the release announcement for the 2022-02-10 > cumulative update release. > > Please review for technical accuracy or if you believe any items should be > added/removed. Please provide feedback no later than 2020-02-10 0:00 AoE[1]. I guess you mean 2022 ;) > * The [`psql`](https://www.postgresql.org/docs/current/app-psql.html) > `\password` command now defaults to setting the password for to the role > defined > by `CURRENT_USER`. Additionally, the role name is now included in the password > prompt. s/for to/for/ > * Build extended statistics for partitioned tables. If you previously added > extended statistics to a partitioned table, you can fix this by running > [`ANALYZE`](https://www.postgresql.org/docs/current/sql-analyze.html). > [`autovacuum`](https://www.postgresql.org/docs/current/routine-vacuuming.html#AUTOVACUUM) > currently does not process these statistics, so you must periodically run > `ANALYZE` on any partitioned tables that are using extended statistics. Instead of "you can fix this" , I suggest to say "you should run ANALYZE on those tables to collect updated statistics." It should say "not process these TABLES" (not stats), and should not say "that are using extended statistics" since partitioned tables should be manually analyzed whether or not they have extended stats. It's good to say "..you should periodically run ANALYZE on partitioned tables to collect updated statistics." (even though this patch doesn't change that). > * Fix crash with > [multiranges](https://www.postgresql.org/docs/current/rangetypes.html) > when extracting a variable-length data types. remove "a" or s/types/types/ > * Disallow altering data type of a partitioned table's columns when the > partitioned table's row type is used as a composite type elsewhere. the data types ? -- Justin
2022-02-10 release announcement draft
Hi, Attached is a draft for the release announcement for the 2022-02-10 cumulative update release. Please review for technical accuracy or if you believe any items should be added/removed. Please provide feedback no later than 2020-02-10 0:00 AoE[1]. Thanks, Jonathan [1] https://en.wikipedia.org/wiki/Anywhere_on_Earth The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 14.2, 13.6, 12.10, 11.15, and 10.20. This release fixes over 55 bugs reported over the last three months. For the full list of changes, please review the [release notes](https://www.postgresql.org/docs/release/). Bug Fixes and Improvements -- This update fixes over 55 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. Included in this release: * Fix for a low probability scenario of index corruption when a HOT ([heap-only tuple](https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/access/heap/README.HOT;hb=HEAD)) chain changes state during `VACUUM`. Encountering this issue is unlikely, but if you are concerned, please consider [reindexing](https://www.postgresql.org/docs/current/sql-reindex.html). * Fix for using [`REINDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-reindex.html) on [TOAST](https://www.postgresql.org/docs/current/storage-toast.html) table indexes to prevent corruption. You can fix any TOAST indexes by [reindexing](https://www.postgresql.org/docs/current/sql-reindex.html) them again. * The [`psql`](https://www.postgresql.org/docs/current/app-psql.html) `\password` command now defaults to setting the password for to the role defined by `CURRENT_USER`. Additionally, the role name is now included in the password prompt. * Build extended statistics for partitioned tables. If you previously added extended statistics to a partitioned table, you can fix this by running [`ANALYZE`](https://www.postgresql.org/docs/current/sql-analyze.html). [`autovacuum`](https://www.postgresql.org/docs/current/routine-vacuuming.html#AUTOVACUUM) currently does not process these statistics, so you must periodically run `ANALYZE` on any partitioned tables that are using extended statistics. * Fix crash with [`ALTER STATISTICS`](https://www.postgresql.org/docs/current/sql-alterstatistics.html) when the statistics object is dropped concurrently. * Fix crash with [multiranges](https://www.postgresql.org/docs/current/rangetypes.html) when extracting a variable-length data types. * Several fixes to the query planner that lead to incorrect query results. * Several fixes for query plan [memoization](https://www.postgresql.org/docs/current/runtime-config-query.html#GUC-ENABLE-MEMOIZE). * Fix startup of a physical replica to tolerate transaction ID wraparound. * When using logical replication, avoid duplicate transmission of a partitioned table's data when the publication includes both the child and parent tables. * Disallow altering data type of a partitioned table's columns when the partitioned table's row type is used as a composite type elsewhere. * Disallow [`ALTER TABLE ... DROP NOT NULL`](https://www.postgresql.org/docs/current/sql-altertable.html) for a column that is part of a replica identity index. * Several fixes for caching that correct logical replication behavior and improve performance. * Fix memory leak when updating expression indexes. * Avoid leaking memory during [`REASSIGN OWNED BY`](https://www.postgresql.org/docs/current/sql-reassign-owned.html) operations that reassign ownership of many objects. * Fix display of whole-row variables appearing in `INSERT ... VALUES` rules. * Fix race condition that could lead to failure to localize error messages that are reported early in multi-threaded use of libpq or ecpglib. * Fix [`psql`](https://www.postgresql.org/docs/current/app-psql.html) `\d` command for identifying parent triggers. * Fix failures on Windows when using the terminal as data source or destination. This affected the psql `\copy` command and using [`pg_recvlogical`](https://www.postgresql.org/docs/current/app-pgrecvlogical.html) with `-f -`. * Fix the [`pg_dump`](https://www.postgresql.org/docs/current/app-pgdump.html) `--inserts` and `--column-inserts` modes to handle tables that contain both generated and dropped columns. * Fix edge cases in how [`postgres_fdw`](https://www.postgresql.org/docs/current/postgres-fdw.html) handles asynchronous queries. These errors could lead to crashes or incorrect results when attempting to run parallel scans of foreign tables. For the full list of changes available, please review the [release notes](https://www.postgresql.org/docs/release/). Updating All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use `pg_upgrade` in order to apply
