pgsql: Allocate access strategy in parallel VACUUM workers.

From: Amit Kapila <akapila(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Allocate access strategy in parallel VACUUM workers.
Date: 2021-04-12 03:35:20
Message-ID: E1lVnM8-00030v-Fa@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Allocate access strategy in parallel VACUUM workers.

Currently, parallel vacuum workers don't use any buffer access strategy.
We can fix it either by propagating the access strategy from a leader or
allow each worker to use BAS_VACUUM access strategy type. We don't see
much use in propagating this information from leader as both leader and
workers are supposed to use the same strategy. We might want to use a
different access strategy for leader and workers but that would be a
separate optimization not suitable for back-branches. This has been fixed
in HEAD as commit f6b8f19a08.

Author: Amit Kapila
Reviewed-by: Sawada Masahiko, Bharath Rupireddy
Discussion: https://postgr.es/m/CAA4eK1KbmJgRV2W3BbzRnKUSrukN7SbqBBriC4RDB5KBhopkGQ@mail.gmail.com

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/48d4a8c88ba73c5e68461d1ced9090ac33827028

Modified Files
--------------
src/backend/access/heap/vacuumlazy.c | 4 ++++
1 file changed, 4 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Kapila 2021-04-12 04:09:59 pgsql: doc: Update information of new messages for logical replication.
Previous Message Michael Paquier 2021-04-12 02:32:30 pgsql: Fix out-of-bound memory access for interval -> char conversion