From 39c879f8758b1246c40f36cb692fd081ea9f43dc Mon Sep 17 00:00:00 2001 From: "Jonathan S. Katz" Date: Wed, 9 Aug 2023 22:15:14 -0400 Subject: [PATCH] Added feedback Reviewed-by: David Rowley Reviewed-by: Erik Rijkers Reviewed-by: Robert Treat Reviewed-by: Noah Misch Reviewed-by: Heikki Linnakangas --- .../current/20230810securityrelease.md | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git a/update_releases/current/20230810securityrelease.md b/update_releases/current/20230810securityrelease.md index 64f9df0..d21d7a2 100644 --- a/update_releases/current/20230810securityrelease.md +++ b/update_releases/current/20230810securityrelease.md @@ -5,7 +5,7 @@ vulnerabilities and over 40 bugs reported over the last several months. If you use [BRIN]((https://www.postgresql.org/docs/current/brin-intro.html)) indexes to look up `NULL` values, you will need to [reindex](https://www.postgresql.org/docs/current/sql-reindex.html) -them after upgrading to this release. You us +them after upgrading to this release. On PostgreSQL 12 and above, you can use [`REINDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-reindex.html) to avoid blocking writes to the affected index and table, for example: @@ -136,11 +136,6 @@ For the full list of changes available, please review the Fixes in PostgreSQL 16 Beta 3 ----------------------------- -The following includes fixes included in PostgreSQL 16 Beta 3: - -* Fix a performance regression when running concurrent -[`COPY`](https://www.postgresql.org/docs/16/sql-copy.html) statements on a -single table. * Add the `\drg` command to `psql` to display information about role grants. * Add timeline ID to filenames generated with `pg_waldump --save-fullpage`. * Fix crash after a deadlock occurs in a parallel `VACUUM` worker. @@ -160,7 +155,7 @@ update its binaries. If you use [BRIN]((https://www.postgresql.org/docs/current/brin-intro.html)) indexes to look up `NULL` values, you will need to [reindex](https://www.postgresql.org/docs/current/sql-reindex.html) -them after upgrading to this release. You us +them after upgrading to this release. On PostgreSQL 12 and above, you can use [`REINDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-reindex.html) to avoid blocking writes to the affected index and table, for example: @@ -168,8 +163,8 @@ to avoid blocking writes to the affected index and table, for example: REINDEX INDEX CONCURRENTLY your_index_name; ``` -Users who have skipped one or more update releases may need to run additional, -post-update steps; please see the release notes for earlier versions for +Users who have skipped one or more update releases may need to run additional +post-update steps; please see the release notes from earlier versions for details. For more details, please see the @@ -179,7 +174,7 @@ Updating to PostgreSQL 16 Beta 3 -------------------------------- To upgrade to PostgreSQL 16 Beta 3 from a previous PostgreSQL 16 Beta version, -or an previous major version of PostgreSQL, you will need to use a strategy +or a previous major version of PostgreSQL, you will need to use a strategy similar to upgrading between major versions of PostgreSQL (e.g. `pg_upgrade` or `pg_dump` / `pg_restore`). For more information, please visit the documentation section on [upgrading](https://www.postgresql.org/docs/16/static/upgrading.html). -- 2.39.5