| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Daniil Davydov <3danissimo(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: test_autovacuum/001_parallel_autovacuum is broken |
| Date: | 2026-04-09 18:21:37 |
| Message-ID: | CAA5RZ0udpvgPMeSTx4H7AUm=QmgE4a0DBLV2AsQPOZjLA1okcg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I think we can enhance these tests using a separate module as Daniil is
> > suggesting, but we should probably get 0001 committed first and then
> > have a quick follow-up. What do you think?
>
> +1. I've pushed the fix.
Thanks!
> It might also be useful if an injection point is activated on the
> particular database rather than cluster-wide.
Here is something that could be discussed for v20 [1]
[1] https://commitfest.postgresql.org/patch/6663/
--
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2026-04-09 18:25:41 | Re: test_autovacuum/001_parallel_autovacuum is broken |
| Previous Message | Masahiko Sawada | 2026-04-09 18:18:45 | Re: test_autovacuum/001_parallel_autovacuum is broken |