Re: test_autovacuum/001_parallel_autovacuum is broken

Sami Imseih <samimseih@gmail.com>

From: Sami Imseih <samimseih@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Daniil Davydov <3danissimo@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2026-04-09T18:21:37Z
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



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix unstable log verification in test_autovacuum.

  2. Remove an unstable wait from parallel autovacuum regression test.