Re: Parallel heap vacuum - Mailing list pgsql-hackers

From John Naylor
Subject Re: Parallel heap vacuum
Date
Msg-id CANWCAZbG7cbppypCo0sVYJMZQ9HmOobKP+aQVU56z8zFFZjQjw@mail.gmail.com
Whole thread Raw
In response to Re: Parallel heap vacuum  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Parallel heap vacuum
List pgsql-hackers
On Thu, Feb 13, 2025 at 5:37 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> During eager vacuum scan, we reset the eager_scan_remaining_fails
> counter when we start to scan the new region. So if we want to make
> parallel heap vacuum behaves exactly the same way as the
> single-progress vacuum in terms of the eager vacuum scan, we would
> need to have the eager_scan_remaining_fails counters for each region
> so that the workers can decrement it corresponding to the region of
> the block that the worker is scanning. But I'm concerned that it makes
> the logic very complex. I'd like to avoid making newly introduced
> codes more complex by adding yet another new code on top of that.

Would it be simpler to make only phase III parallel? In other words,
how much of the infrastructure and complexity needed for parallel
phase I is also needed for phase III?

--
John Naylor
Amazon Web Services



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Confine vacuum skip logic to lazy_scan_skip
Next
From: Amit Kapila
Date:
Subject: Re: DOCS - inactive_since field readability