Add runtime checks for bogus multixact offsets master github/master
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>
Thu, 11 Dec 2025 09:18:14 +0000 (11:18 +0200)
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>
Thu, 11 Dec 2025 09:18:14 +0000 (11:18 +0200)
commitd4b7bde4183bc39c6d7a22d22188fc4aab2ba8d1
tree20d215fc2477fdf7fbefa36c78e4f29568859d86
parent795e94c70cf13f60b2cb4010f29a1bca542d2031
Add runtime checks for bogus multixact offsets

It's not far-fetched that we'd try to read a multixid with an invalid
offset in case of bugs or corruption. Or if you call
pg_get_multixact_members() after a crash that left behind invalid but
unused multixids. Better to get a somewhat descriptive error message
if that happens.

Discussion: https://www.postgresql.org/message-id/3624730d-6dae-42bf-9458-76c4c965fb27@iki.fi
src/backend/access/transam/multixact.c