From 4d8dff733f49d7c47c34622ba14f76240a7f5cd8 Mon Sep 17 00:00:00 2001 From: "Jonathan S. Katz" Date: Mon, 13 Jun 2022 21:14:26 -0400 Subject: [PATCH] Update to 2022-06-16 draft Reviewed-by: Tom Lane --- update_releases/current/20220616updaterelease.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/update_releases/current/20220616updaterelease.md b/update_releases/current/20220616updaterelease.md index 35f1d4e..6b0a294 100644 --- a/update_releases/current/20220616updaterelease.md +++ b/update_releases/current/20220616updaterelease.md @@ -1,7 +1,7 @@ The PostgreSQL Global Development Group has released PostgreSQL 14.4 to fix an issue that could cause silent data corruption when using the [`CREATE INDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-createindex.html) -and [`REINDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-reindex.html) +or [`REINDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-reindex.html) commands. Please see the following section for information on how to detect and correct silent data corruption in your indexes. @@ -16,12 +16,14 @@ versions of PostgreSQL (10 - 14). Detect and Fix `CREATE INDEX CONCURRENTLY` / `REINDEX CONCURRENTLY` Corruption ------------------------------------------------------------------------------ -PostgreSQL 14.4 fixes an issue with the +PostgreSQL 14.4 fixes an issue with [`CREATE INDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-createindex.html) and [`REINDEX CONCURRENTLY`](https://www.postgresql.org/docs/current/sql-reindex.html) -that could cause silent data corruption of indexes. This issue may not have -corrupted your indexes, but if you are unsure, we advise you to reindex using -the instructions below. +that could cause silent data corruption of indexes. Prior to the fix, +`CREATE INDEX CONCURRENTLY` and `REINDEX CONCURRENTLY` could build indexes that +would have missing entries, causing `SELECT` queries that used the index to not +find certain rows. This issue may not have corrupted your indexes, but if you +are unsure, we advise you to reindex using the instructions below. You can detect if a B-tree index (the default index type) has data corruption using the [`pg_amcheck`](https://www.postgresql.org/docs/current/app-pgamcheck.html) @@ -70,8 +72,8 @@ function that returns a domain over composite type. sub-`SELECT` that is referenced in a `GROUPING` function. * Fix error checking in `COPY FROM` when the database encoding is `SQL_ASCII` but the client encoding is a multi-byte encoding. -* Report implicitly-created operator families (`CREATE OPERATOR CLASS`) to event -triggers. +* Report implicitly-created operator families (generated by +`CREATE OPERATOR CLASS`) to event triggers. * Prevent triggering `wal_receiver_timeout` on a standby during logical replication of large transactions. * Remove incorrect TLS private key file ownership check in libpq. -- 2.39.5