| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Jeremy Schneider <schnjere(at)amazon(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code) |
| Date: | 2020-08-27 23:47:11 |
| Message-ID: | CAH2-Wz=8RtReZ=GsDqtRj6YRAy5RLsAi3wA+FdgCcdUXeuej+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 26, 2020 at 12:16 PM Alvaro Herrera
<alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2020-08-27 23:50:26 | Re: Clang Address Sanitizer (Postgres14) Detected Memory Leaks |
| Previous Message | Tatsuro Yamada | 2020-08-27 23:42:55 | Re: list of extended statistics on psql |