Re: Set access strategy for parallel vacuum workers

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>
Subject: Re: Set access strategy for parallel vacuum workers
Date: 2021-04-07 11:41:23
Message-ID: CAD21AoCrLY-2-y6U_cnfjfDG8Nb_MbPNP03x4Yo-Ze-+tu7CjA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 7, 2021 at 7:00 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)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.

Regards,

--
Masahiko Sawada
EDB: https://www.enterprisedb.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2021-04-07 11:44:32 Re: MultiXact\SLRU buffers configuration
Previous Message Magnus Hagander 2021-04-07 11:32:37 Re: hba.c:3160:18: warning: comparison of unsigned enum expression