Tomas Vondra e3fcca0d0d Revert changes in HOT handling of BRIN indexes ... This reverts commits 5753d4ee32 and fe60b67250 that modified HOT to ignore BRIN indexes. The commit message for 5753d4ee32 claims that: When determining whether an index update may be skipped by using HOT, we can ignore attributes indexed only by BRIN indexes. There are no index pointers to individual tuples in BRIN, and the page range summary will be updated anyway as it relies on visibility info. This is partially incorrect - it's true BRIN indexes don't point to individual tuples, so HOT chains are not an issue, but the visibitlity info is not sufficient to keep the index up to date. This can easily result in corrupted indexes, as demonstrated in the hackers thread. This does not mean relaxing the HOT restrictions for BRIN is a lost cause, but it needs to handle the two aspects (allowing HOT chains and updating the page range summaries) as separate. But that requires a major changes, and it's too late for that in the current dev cycle. Reported-by: Tomas Vondra Discussion: https://postgr.es/m/05ebcb44-f383-86e3-4f31-0a97a55634cf@enterprisedb.com		2022-06-16 15:02:49 +02:00
..
src	Revert changes in HOT handling of BRIN indexes	2022-06-16 15:02:49 +02:00
KNOWN_BUGS	…
MISSING_FEATURES	…
Makefile	…
TODO	Change documentation references to PG website to use https: not http:	2017-05-20 21:50:47 -04:00