Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers

From: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Subject: Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers
Date: 2026-09-29 13:47:54
Message-ID: CAN12+Y+R0omTVoPLvosfV7ZEB6o1ycWLEi6CsnQRciWfCvjW2w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> One nit, please feel free to ignore it. VacuumUpdateCosts() prints
> yes/no for booleans, so on/off here could match that for consistency.
> AFAICS, there is no hard rule, and I am fine with it as is.

Better to be consistent here. Attached is v3-, which also updates the test
output expected.

--
Sami Imseih
Amazon Web Services (AWS)

Attachment Content-Type Size
v3-0001-Propagate-track_cost_delay_timing-to-parallel-aut.patch application/octet-stream 4.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-09-29 13:50:17 Re: pg_resetwal: Fix handling of commit timestamp XIDs
Previous Message John Naylor 2026-09-29 13:38:48 Re: BUG #19597: getQuadrant: impossible case is reachable