Re: autovacuum: automatically propagate updated parameters

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: autovacuum: automatically propagate updated parameters
Date: 2026-08-27 11:57:02
Message-ID: 55A4E54D-D167-4057-89DA-649C9F8D3F6F@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 27 Aug 2026, at 10:37, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
>
>> we can stop the
>> second worker at the injection point "vacuum-truncate-enabled" for
>> example. While it works and we can reduce the filler table size, it
>> would add an unclear dependency as vacuum-truncate-enabled is not
>> related to parallel autovacuum.
>
> I added a new injection point and stopped it there in v3. If you think
> that's unnecessary, we can replace it to vacuum-truncate-enabled in
> the test and remove the injection point, and it works the same way.
> This just seemed cleaner to me.

I prefer this approach, injection points are cheap enough that we don't need to
reuse and cause undefined dependencies. I'll try to get this applied later today.

--
Daniel Gustafsson

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Fujii Masao 2026-08-27 10:30:27 Re: to_char() on integer with V format silently wraps on overflow