Re: autovacuum launcher crash: assert in pgstat_count_io_op (IOOP_EXTEND on pg_database's VM)

From: Ewan Young <kdbase(dot)hack(at)gmail(dot)com>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: autovacuum launcher crash: assert in pgstat_count_io_op (IOOP_EXTEND on pg_database's VM)
Date: 2026-06-30 05:41:43
Message-ID: CAON2xHMOnx3MN-TgKRmwn9H+gaZJz0YyvYYzPRnobV7JNaDtYA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 25, 2026 at 2:59 AM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> On Tue, Jun 2, 2026 at 10:03 AM Ewan Young <kdbase(dot)hack(at)gmail(dot)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.

Thanks, Melanie — glad it's resolved, and thanks for the turnaround
and the credit!

>
> - Melanie

Regards,
Ewan Young

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2026-06-30 05:56:04 Re: Per-thread leak in ECPG's memory.c
Previous Message Amit Kapila 2026-06-30 05:32:27 Re: Proposal: Conflict log history table for Logical Replication