Adjusted 2022-02-10 release announcement per feedback
authorJonathan S. Katz <jonathan.katz@excoventures.com>
Tue, 8 Feb 2022 01:39:48 +0000 (20:39 -0500)
committerJonathan S. Katz <jonathan.katz@excoventures.com>
Tue, 8 Feb 2022 01:39:48 +0000 (20:39 -0500)
Reviewe-by: Justin Pryzby <pryzby@telsasoft.com>
update_releases/current/20220210updaterelease.md

index 895e8e8f342e947ac83defe1b64f72a0bb28d175..54e206fba63b73a38ed49245b54f5891d3643422 100644 (file)
@@ -25,19 +25,20 @@ 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
+`\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 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.
+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.
+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.