| From: | Manu <manuelreyesbravo(at)gmail(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: autovacuum: automatically propagate updated parameters |
| Date: | 2026-09-25 22:03:24 |
| Message-ID: | 179037380436.2378773.9309414664849248903@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> I'm fine leaving 0002 here for the record, since I haven't
> reviewed it in depth and I don't think it has had a close review yet,
I ran v3 0001+0002 on REL_19_STABLE (407687a0fb1), with assertions and
injection points. 001_parallel_autovacuum.pl and
003_cost_reload_while_waiting.pl passed 10 runs out of 10.
As a control I removed only the SetLatch() loop that 0001 adds to
autovac_recalculate_workers_for_balance(). Then test 5 in 001 times
out waiting for parallel-autovacuum-leader-cost-updated, while 003
still passes. So 003 covers the reload path and test 5 the rebalance
path, each on its own.
The opposite case, a worker leaving the balance while the leader
waits, is not covered. I tried a test for it and could not make it
deterministic: with autovacuum_naptime = 1s the launcher starts other
workers, and one of them joining the balance wakes the leader too, so
the test passed even with the launcher's wakeup removed.
Regards,
Manu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-09-25 23:53:45 | Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange |
| Previous Message | Bharath Rupireddy | 2026-09-25 21:41:39 | Re: autovacuum: automatically propagate updated parameters |