Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code)

On Wed, Aug 26, 2020 at 12:16 PM Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> We could do this in stable branches, if there were any reports that
> this inconsistency is happening in real world databases.

I hope that the new heapam amcheck stuff eventually leads to our
having total (or near total) certainty about what correct on-disk
states are possible, regardless of the exact pg_upgrade + minor
version paths. We should take a strict line on this stuff where
possible. If that turns out to be wrong in some detail, then it's
relatively easy to fix as a bug in amcheck itself.

There is a high cost to allowing ambiguity about what heapam states
are truly legal/possible. It makes future development projects harder.

-- 
Peter Geoghegan