> On 29 Jul 2026, at 10:00, Alexander Lakhin <[email protected]> wrote:
>
> Looks like it is not immune to autovacuum.
How about running the module's isolation tests with autovacuum = off
in a temp config? pg_freespacemap does exactly that for the same
reason (VACUUM-dependent output), test_decoding does a softer variant
(autovacuum_naptime = 1d).
Also, as a wild idea, the pages expected to be deleted could be filled
from a rolled-back transaction instead of DELETE+VACUUM of committed rows -
aborted tuples are removable regardless of concurrent snapshots. But I did
not try it with this particular test.
Best regards, Andrey Borodin.
