On Sat, May 30, 2026 at 11:31 AM Scott Ray <[email protected]> wrote: > > > I guess the overhead of one more scan of the process array for every > > autovacuum > > run if "log_autovacuum_min_duration" is non-zero (which is the default) > > is acceptable. > > > Could vacuum compute the blocker during ComputeXidHorizons and consume it at > log time? > Avoids the extra scan, and binds the blocker to the horizon vacuum used for > pruning.
As Sami suggested in [0], I think this design is a cleaner approach because it separates the responsibilities of ComputeXidHorizons and the calculation of vacuum blockers. [0] https://www.postgresql.org/message-id/CAA5RZ0s%2BUUXekbeGcC-H71kW%3DMfeaUCOV%3DyEWX94NXViO2-%3DpA%40mail.gmail.com -- Best regards, Shinya Kato NTT OSS Center
