Re: Set access strategy for parallel vacuum workers - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Set access strategy for parallel vacuum workers
Date
Msg-id CAA4eK1JBQHRRXXOBoU1x7m2ApYoCUczDvbqwb2TW9hmJ4-srDg@mail.gmail.com
Whole thread Raw
In response to Re: Set access strategy for parallel vacuum workers  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Set access strategy for parallel vacuum workers  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Wed, Apr 7, 2021 at 5:11 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> On Wed, Apr 7, 2021 at 7:00 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> > During recent developments in the vacuum, it has been noticed [1] that
> > parallel vacuum workers don't use any buffer access strategy. I think
> > we can fix it either by propagating the required information from the
> > leader or just get the access strategy in each worker separately. The
> > patches for both approaches for PG-13 are attached.
>
> Thank you for starting the new thread.
>
> I'd prefer to just have parallel vacuum workers get BAS_VACUUM buffer
> access strategy. If we want to have set different buffer access
> strategies or ring buffer sizes for the leader and worker processes,
> the former approach would be better. But I think we're unlikely to
> want to do that, especially in back branches.
>

Fair enough. Just to be clear, you prefer to go with
fix_access_strategy_workers_11.patch, right?

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Set access strategy for parallel vacuum workers
Next
From: Masahiko Sawada
Date:
Subject: Re: Set access strategy for parallel vacuum workers