Hi, On Thu, Oct 1, 2026 at 5:20 AM Shinya Kato <[email protected]> wrote: > > I presented this patch at PostgreSQL Developer Meeting [1], an offline > event in Japan, and Fujii-san gave me the following comments. > > 1. If the blocker is looked up right after the cutoff is computed, one > extra scan is enough. > 2. Information that needs a second lookup, such as the active versus > idle state and the prepared transaction GID, is out of scope for this > patch and should come as a follow-up. > 3. Do not widen the scope of the patch. > > v10 addresses all three.
Thanks for the updated patch. Sorry for the delay. I have been thinking about how useful reporting the per-vacuum blocker will be with the pg_xmin_horizon view proposed in the other thread. Why can't users find the blockers with the view and the removable cutoff that is already reported in the verbose log output? Maybe we want this for historical purposes (?). IMHO, a separate proc array scan is not the way to go for a couple of reasons. It may not report the reason that was factored into the cutoff when it was computed, and it may not be optimal to do another proc array and slot scan with their locks in the vacuum path. Thoughts? -- Bharath Rupireddy Amazon Web Services: https://aws.amazon.com
