| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Smolkin Grigory <smallkeen(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: race condition in pg_class |
| Date: | 2024-05-13 19:53:08 |
| Message-ID: | CA+TgmoZocjvRKB5Rv-8oJ5=-FVaSeFSUCC5C3HN2ZPjgZPS=jA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, May 12, 2024 at 7:29 PM Noah Misch <noah(at)leadboat(dot)com> wrote:
> - [consequences limited to transient failure] Since a PROC_IN_VACUUM backend's
> xmin does not stop pruning, an MVCC scan in that backend can find zero
> tuples when one is live. This is like what all backends got in the days of
> SnapshotNow catalog scans. See the pgbench test suite addition. (Perhaps
> the fix is to make VACUUM do its MVCC scans outside of PROC_IN_VACUUM,
> setting that flag later and unsetting it earlier.)
Are you saying that this is a problem already, or that the patch
causes it to start happening? If it's the former, that's horrible. If
it's the latter, I'd say that is a fatal defect.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-05-13 20:17:30 | Re: Why is citext/regress failing on hamerkop? |
| Previous Message | Robert Haas | 2024-05-13 19:43:24 | Re: WAL_LOG CREATE DATABASE strategy broken for non-standard page layouts |