| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: autovacuum: automatically propagate updated parameters |
| Date: | 2026-08-27 08:37:25 |
| Message-ID: | CAN4CZFPoQrT2ddLUiJXmJ5o80YF9LN_3m9PL4QCX_bddj44uGA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> 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.
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Propagate-rebalanced-cost-limit-to-parallel-vacuu.patch | application/octet-stream | 6.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Rachitskiy | 2026-08-27 08:49:09 | Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations |
| Previous Message | Andrey Borodin | 2026-08-27 08:16:22 | Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations |