Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wb4XS-002HE1-0y for pgsql-bugs@arkaria.postgresql.org; Sat, 20 Jun 2026 22:51:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wb4XP-002Q3y-0a for pgsql-bugs@arkaria.postgresql.org; Sat, 20 Jun 2026 22:51:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wb4XO-002Q3n-0o for pgsql-bugs@lists.postgresql.org; Sat, 20 Jun 2026 22:51:42 +0000 Received: from fout-b5-smtp.messagingengine.com ([202.12.124.148]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wb4XK-00000001UwX-231u for pgsql-bugs@lists.postgresql.org; Sat, 20 Jun 2026 22:51:41 +0000 Received: from phl-compute-09.internal (phl-compute-09.internal [10.202.2.49]) by mailfout.stl.internal (Postfix) with ESMTP id B429A1D0006D; Sat, 20 Jun 2026 18:51:34 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-09.internal (MEProxy); Sat, 20 Jun 2026 18:51:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1781995894; x=1782082294; bh=FE8JlJ5Aj3 Yu4a/FlXOL8ZWctqjHPsW73M6kbBm9geI=; b=xYoQchFrSUfuZmj0sS/tMIyrWb vojM4WdgM8ZHmX6jx425vnB9pJEF6/UaK1UAlMFn4o0tHsh+d6zCM5h9xk/tzjIu 2TI3b2oTp+a5ZvEo+KigvyD7bobR55ZN6skrwYwZOf1l6iprGL39bArBDlavCWf+ bP/6W6DC5xVKciSweQfQx7kr5HpC0k+94B0y1nx75diFjmsRPR+bILPLn8+Gm0or hL/27VqQljMwKzKrbG3XFG6EB66tFV4Z1ZXn39/D/an40s4vlM6qgVno41iSWXGX U6pX+g64hATkBxuMNl/ktYC5BikmKfh7QAX89/KiV4Of6u/sk/Zx7tqXN8nQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1781995894; x=1782082294; bh=FE8JlJ5Aj3Yu4a/FlXOL8ZWctqjHPsW73M6 kbBm9geI=; b=aEOSmKusMmA1MPVSNgmlS9jho/iDYXvWBvezbZExrvc9mQaF67E GTqjixUO7N74guvw/EnsIiu+M6sAVnVnMZmrLihhL4gtxOVfs8wWTXgHXWXO6kvh POgk6ET+mBxtIixbh3LMFms65tvE/pbcdiaJm791rgcLcx89ksHgcCEByrtOjTnm Yq2IR9thni6IlmwrSU/2+MkxdANhc/ARU1JiqHSm6uDxg1SHokZduPrGCb/cllwT jaH+3Fj90Oo3k0481MSwJJFXfA3bTZJEDCm/U+ZR4YhGS1KeYtF9u/uW908DZn9j 6OEK7+Pod36CP3f38KiCOf0zfCuZ5ip8GCA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTG2Suw45mAI7VI9nurlaZpmZD0VlLGTHGm5vvA3k2ZR0K2Fww4WNCdw0Y4ZOMflNg 0CwINqTxUxAaSNCwwBo300w2/GO/ZyGZ3UA/8qfLvqj7AECy5a+HlNPi39rtNWNz/+rg/c pkAdvW1AmOCrn5V6s4n7QRUxGeXutmk/0n8grbdnI+HRMBTpT4tpnDOmQq+qvKvQBdGsL0 UrhUn69tUN+y9sl/duyzz50rEKTf2MjJTVshCXFUUV8Qu7SEk85FuM0vjo68gg7WcmdUQJ PI/qTLFpQamIi3yH9LzuKd71UpAvSG4ALdj60Qtk046RE1R+JIrsor8gKcNZmaQbe0Q0Eq qXJuwo6Z4UGzuJBMyYZjNtNf5OJ3Du5U10BeKObe3O2ta8/J1A3z1sJY6S7kPNSf8yR4gf Md/Bgo1D/8ilsNB2Pz5gY25COa+6kbOVGLlOsPp/NaEaDRZ+gbLlinwM7Q7V/I6wBUM5xq QVcepfJ3o9LO/6lw8/wrbohNjXKopg4PREAjoOOQmbBgEScaRokf4f1ntwOZdq7rF6LdL8 N5glFY+gcH4LW880mJz/Amb1BJt4zUnFPQIA2Nh7GxwdI+Otb2mXKa7EwLNEyJBxJRHEZ9 mG9BoSEhZRrT267cC6ckZY5P4OUz+DQzdk/RrckK/jX94QM3r/OL9vWEyJfQ X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 20 Jun 2026 18:51:31 -0400 (EDT) Date: Sun, 21 Jun 2026 07:51:25 +0900 From: Michael Paquier To: =?iso-8859-1?Q?=C1lvaro?= Herrera Cc: Ayush Tiwari , Sami Imseih , zlh21343@163.com, pgsql-bugs@lists.postgresql.org, Andres Freund , Kyotaro Horiguchi Subject: Re: BUG #19520: PANIC when concurrently manipulating stored procedures with pg_stat_statements and track_functions = Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2choOSa2ofoPKvJw" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --2choOSa2ofoPKvJw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 20, 2026 at 06:58:27PM +0200, Alvaro Herrera wrote: > Yeah, this sounds more or less reasonable. The callers that pass > missing_ok=3Dfalse could still use the original function name though, no? >=20 > (Personally I would do for an ABI compatibility in back branches with > this new function, and an API breakage in master by simply adding the > new argument everywhere, but keeping the old function name. This way we > don't preserve unnecessary API ugliness forever.) Yes, that would be the idea: - On HEAD, keep the old function name, add the parameter. - On the back-branches, use the new function name with the new parameter. And contrary to you limit the use of the old function name. Using the old function name in the back-branches where missing_ok is false would also work, of course. My suggestion just makes one less call showing up on the stack. The previous patch posted is not for HEAD, only for v15~v18. -- Michael --2choOSa2ofoPKvJw Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmo3GW0ACgkQnvQgOdby QH0s6A/+Pr/yIx4Pe/n7132eI0V2Qm5uDo/vpCzCWPsHOOQPfwAE9ZoQJ2mq/Urz fflwwUUzU3f3gb7QL65+eU+i5cPvn55GwNteoQMb9aUTvs4B1yhUfSCdWaow/9zh 2jszxpNTcQc9YQWPexfItCQJ6jrlN9f/VklbGZ5M5GzBr7D+D5h6iO7kUlCvFRJP NnnbU1E5CZxoE0X+I232e71Sp0m+5Uz9hUcgikWrMw5H2zEFlM7+NBv3EsPObQgb rslGwKo7+iJiopjOuUOwnespyqTy2rIsdnfD8+r6KP6ucsZ5Xxug6b1buPlnp56y 6kmTFQKybQTR3C8+Si4uy9MUDpR7Ug8FuD+yoxC+0Qt3RUfpvMLOqkD02BVmo4ge LK0k+gb9rBtOkp61pLxWECzj58MQ+FylJgluXtzw/cX/dY0lcy2g5syLlgBsbcTU hLpCHUnpx7Lo+P2vjHwPE6bsTv3Vl7aRSGqMSUC19QWmGtxj0d0ss7CVwcLB9Bd0 UGyORx1JvCpB7SxfcfxuV2/IvpY6F++d+UCcE6afZr+vYAM6r8d2u4JrCrxYs4oz 0s5u3Sim3LZBiPXTY1FM+ir7m0kHPrV50IRWgIGxqIyd6w9Yzg6Ro3cq9xiLATpG yfnMykD70SRWd30tTu18CltJm4tNMgXT7tyUNoyBC7GAq10bAYc= =+N/V -----END PGP SIGNATURE----- --2choOSa2ofoPKvJw--