Re: HOT chain validation in verify_heapam()

Aleksander Alekseev <aleksander@timescale.com>

From: Aleksander Alekseev <aleksander@timescale.com>

To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Cc: Himanshu Upadhyaya <upadhyaya.himanshu@gmail.com>, Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>

Date: 2023-01-19T13:55:18Z

Lists: pgsql-hackers

Hi hackers,

> Fixed.

I noticed that this patch stuck a little and decided to take another look.

It seems to be well written, covered with tests and my understanding
is that all the previous feedback was accounted for. To your knowledge
is there anything that prevents us from moving it to "Ready for
Committer"?

-- 
Best regards,
Aleksander Alekseev

Commits

amcheck: Generalize one of the recently-added update chain checks.
- c87aff065c33 16.0 landed
amcheck: Tighten up validation of redirect line pointers.
- 80d5e3a61551 16.0 landed
amcheck: Fix verify_heapam for tuples where xmin or xmax is 0.
- 8fd5aa76c367 14.8 landed
- 701ec5557968 15.3 landed
- e88754a1965c 16.0 landed
amcheck: Fix a few bugs in new update chain validation.
- 949e2e7c4f68 16.0 landed
Fix new test case to work on (some?) big-endian architectures.
- c75a623304bc 16.0 landed
Don't test HEAP_XMAX_INVALID when freezing xmax.
- 02d647bbf057 16.0 landed