On Tue, Apr 7, 2026 at 8:49 PM Amit Kapila <[email protected]> wrote: > > On Tue, Apr 7, 2026 at 7:49 PM Antonin Houska <[email protected]> wrote: > > > > Hayato Kuroda (Fujitsu) <[email protected]> wrote: > > > > > 02. SnapBuildProcessRunningXacts > > > > > > Per my understanding, the db_specic snapshot can be also serialized. Is it > > > possibility tha normal logical decoding system restores the snapshot and > > > obtain > > > the wrong result? > > > > I don't think that the database-specific xl_running_xacts WAL record affects > > what SnapBuildSerialize() writes to disk: the contents of > > builder->committed, > > etc. is updated by decoding COMMIT and ABORT records. > > > > I think the point is that the other process say a walsender could > restore such a snapshot making it take the wrong decision. >
Right. I think it affects even concurrent REPACK (CONCURRENTLY) running on other databases. They could end up restoring the snapshot serialized by another REPACK command running on another database and becoming the consistent state without waiting for transactions concurrently running on the same database, which is clearly wrong. Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com
