Re: autovacuum launcher crash: assert in pgstat_count_io_op (IOOP_EXTEND on pg_database's VM) - Mailing list pgsql-hackers

From Melanie Plageman
Subject Re: autovacuum launcher crash: assert in pgstat_count_io_op (IOOP_EXTEND on pg_database's VM)
Date
Msg-id CAAKRu_abOOp8yMi5czfEmtANOFbbS-2TQ1VtyQXi8iKiEm48Uw@mail.gmail.com
Whole thread
In response to Re: autovacuum launcher crash: assert in pgstat_count_io_op (IOOP_EXTEND on pg_database's VM)  (Ewan Young <kdbase.hack@gmail.com>)
Responses Re: autovacuum launcher crash: assert in pgstat_count_io_op (IOOP_EXTEND on pg_database's VM)
List pgsql-hackers
On Tue, Jun 2, 2026 at 10:03 AM Ewan Young <kdbase.hack@gmail.com> wrote:
>
> That all makes sense — your plan sounds right to me. Happy to go with
> relaxing pgstat_tracks_io_op() for 19 and leaving the
> table_beginscan_catalog() flags work for 20, and to drop my patch.
>
> Reproducer attached.
>
> Thanks so much for the quick and thoughtful response — really appreciate it!

Thanks for the report and reproducer! The fix for 19 we discussed is
now committed in 4abf411e232 (and I've marked the open item closed).
I've added a note to my personal to-do for 20 to enable setting the VM
on-access for catalog tables, but feel free to propose a patch if
you'd like.

- Melanie



pgsql-hackers by date:

Previous
From: Marcos Pegoraro
Date:
Subject: Re: Get rid of "Section.N.N.N" on DOCs
Next
From: "Tristan Partin"
Date:
Subject: Re: Add MIN/MAX aggregate support for uuid