| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(dot)pg(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 15:45:17 |
| Message-ID: | CALj2ACUJpc+9TxGtuYR8q4bf0Nxj2CdvygehSuuJWvOEVZbOCA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Tue, Sep 29, 2026 at 6:48 AM Sami Imseih <samimseih(dot)pg(at)gmail(dot)com> wrote:
>
> > 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.
Thanks. v3 path looks good to me.
--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manu | 2026-09-29 16:08:24 | Re: ATTACH PARTITION cost grows linearly with pg_constraint size (seqscan in CloneFkReferenced), much worse since not-null constraints are in pg_constraint (PG 18) |
| Previous Message | Anthonin Bonnefoy | 2026-09-29 15:37:46 | Re: Protocol Compression (fourth attempt) |