Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions = - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
Date
Msg-id ajOE3uRxVgSlPRcw@paquier.xyz
Whole thread
In response to Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =  (Ayush Tiwari <ayushtiwari.slg01@gmail.com>)
List pgsql-bugs
On Thu, Jun 18, 2026 at 08:52:49AM +0530, Ayush Tiwari wrote:
> The v2 patch looks fine to me. Tested it, no PANICs.

The buildfarm has backfired with the ABI compliance check, which has
made me double-check for some extension code where the API change
would matter, based on this list:
https://wiki.postgresql.org/wiki/CustomCumulativeStats

And I did see one spot here, where there is a
pgstat_custom_drop_entry() that maps to a definition of
pgstat_drop_entry():
https://github.com/pganalyze/pg_stat_plans

I'll go file a ticket.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: 王跃林
Date:
Subject: Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
Next
From: Amit Langote
Date:
Subject: Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables