e8704075ff
This release fixes an issue with all versions of PostgreSQL 14 that can lead to silent corruption of indexes. Since the release of PostgreSQL 14.0, there existed an issue with CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY that could cause silent data corruption in indexes. This issue is fixed in the upcoming PostgreSQL 14.4 release. If you ran either of these commands on any version of PostgreSQL 14 prior to 14.4, you may have experienced silent data corruption. You can use the pg_amcheck command with the --heapallindexed flag to detect this issue with B-tree indexes. If you need an immediate remediation for this issue before the PostgreSQL 14.4 release, you can run CREATE INDEX or REINDEX without CONCURRENTLY. You can also run the reindexdb command and use the --jobs flag for added parallelism, but do not use the --concurrently flag. Once PostgreSQL 14.4 is released, you can safely use CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY to manage your indexes, as well as the --concurrently flag on reindexdb. URL: https://www.postgresql.org/message-id/165473835807.573551.1512237163040609764%40wrigleys.postgresql.org
3 lines
187 B
Text
3 lines
187 B
Text
TIMESTAMP = 1655233048
|
|
SHA256 (postgresql/postgresql-14.4.tar.bz2) = c23b6237c5231c791511bdc79098617d6852e9e3bdf360efd8b5d15a1a3d8f6a
|
|
SIZE (postgresql/postgresql-14.4.tar.bz2) = 22094218
|