Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>, zlh21343(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Subject: Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions =
Date: 2026-06-22 23:12:35
Message-ID: ajnBY9nIEpGSFLB2@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jun 22, 2026 at 05:28:58PM +0900, Michael Paquier wrote:
> By the way, regarding .abi-compliance-history, I am planning to remove
> the latest entry after reading how ABICompCheck.pm works in the
> buildfarm code. It uses the latest commit as a base point of
> comparison, and compares it with the latest commit specified in the
> ABI file.

And adjusted things on v15~v18 as of fe464e9e6863.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Andres Freund 2026-06-22 20:53:37 Re: BUG #19505: Some weird spikes postgresql processes in database (up to 200k sometime) without apparent reasons.