postgresql/contrib/amcheck
Noah Misch 2e33b43599 Avoid race in RelationBuildDesc() affecting CREATE INDEX CONCURRENTLY.
CIC and REINDEX CONCURRENTLY assume backends see their catalog changes
no later than each backend's next transaction start.  That failed to
hold when a backend absorbed a relevant invalidation in the middle of
running RelationBuildDesc() on the CIC index.  Queries that use the
resulting index can silently fail to find rows.  Fix this for future
index builds by making RelationBuildDesc() loop until it finishes
without accepting a relevant invalidation.  It may be necessary to
reindex to recover from past occurrences; REINDEX CONCURRENTLY suffices.
Back-patch to 9.6 (all supported versions).

Noah Misch and Andrey Borodin, reviewed (in earlier versions) by Andres
Freund.

Discussion: https://postgr.es/m/20210730022548.GA1940096@gust.leadboat.com
2021-10-23 18:36:42 -07:00
..
expected Restore lost amcheck TOAST test coverage. 2020-07-31 15:34:26 -07:00
sql Restore lost amcheck TOAST test coverage. 2020-07-31 15:34:26 -07:00
t Avoid race in RelationBuildDesc() affecting CREATE INDEX CONCURRENTLY. 2021-10-23 18:36:42 -07:00
.gitignore
amcheck--1.0--1.1.sql
amcheck--1.0.sql
amcheck--1.1--1.2.sql
amcheck.control
Makefile Avoid race in RelationBuildDesc() affecting CREATE INDEX CONCURRENTLY. 2021-10-23 18:36:42 -07:00
verify_nbtree.c Fix amcheck child check pg_upgrade bug. 2020-09-16 10:42:28 -07:00