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 1wba4p-002gDr-3D for pgsql-bugs@arkaria.postgresql.org; Mon, 22 Jun 2026 08:32:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wba4o-005RDx-2r for pgsql-bugs@arkaria.postgresql.org; Mon, 22 Jun 2026 08:32:18 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wba1k-005OF2-1p for pgsql-bugs@lists.postgresql.org; Mon, 22 Jun 2026 08:29:08 +0000 Received: from fhigh-a5-smtp.messagingengine.com ([103.168.172.156]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wba1j-00000001YmB-0X6l for pgsql-bugs@lists.postgresql.org; Mon, 22 Jun 2026 08:29:07 +0000 Received: from phl-compute-09.internal (phl-compute-09.internal [10.202.2.49]) by mailfhigh.phl.internal (Postfix) with ESMTP id B867F14001E5; Mon, 22 Jun 2026 04:29:05 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-09.internal (MEProxy); Mon, 22 Jun 2026 04:29:05 -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=1782116945; x=1782203345; bh=2y+6wYY/34 GEuV5oiOIJuV8G3TD8jR6s9wPd5ptegM0=; b=ix9cR7LC6eaO9hOFA6xL60thqM +GAJcGsrMEwaiAUN40M8MGt5C7a9R2YQKpuz3Wb1DTf6T0H0vsIuWDub+hEyN0Jh GGy4DqpqFxxIdaX4tjwTxbB84qKnsgB+IyHy4jekW/ZV0eFJXy5fTk9GwVLzB+jK 1C7x3q6IVHNwju4t/LTgPI5dh9Sgz5m+kmEP0nm2g1SUizsc/B02uYh+v1KxiGR2 5hAtYnUfNwBjYc4hW2nRuEYMjCsSniYA3awAxu+ZLc48dsm6p4BW1cWgi3wK0wRJ yqtvcv/VN7fzD+dKQGSPHhWgoyi5A6lBsJzJj+feQ7ff4RxbbbjNe5QG1u9w== 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= 1782116945; x=1782203345; bh=2y+6wYY/34GEuV5oiOIJuV8G3TD8jR6s9wP d5ptegM0=; b=WJL27vJVMrDRcfcwuBVA8+3h82Qm2neCNuyIlsKBjRCaJzi2lqU 0FL0Z3f7/yxCBgmV0O53JeANocHECX06UX9qjImd1CIGnVR6Qc4i3KwGVM6mjeLy CvNZ0Er276H3sMlxhRRSeAPpO9YXwgIpCvQ0oQLk/i//eG/qcHHsS+WRoiG2uVPZ nuFDO61VHdbvtO9y8Vw00KErKI89ZvF85e95Ck0rGPUBOwk7dT+XfxT0ol4pVQjL gvkQEz0QpGpakC0aTjEjlO2J3UzMK95ddR30kPFtWN0MEUPhoAf8V4uUN8Pr8d06 jzR5NEKo2xWT1sbBloXin7qW+lX5+pWG2vQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTFoVwFEaSeQs92B5chT1HiFtft7igGHt97ApmmFWaO1AXd83HCJb64Jf0PYi72RaF ZA1B2M5y3wN3n7i4DqOEiBYYgLrrpWyYjVSp+o4P6tdYOC79PpcWJbok7MIpJHGTWAPYK+ CpODcc9qfa3En+2M5x3NjziRkshZWJj4JxpCR9fFGVeJIOQc7PnzerGDVauxpoTWaaEsLZ x0yeX2OREPFMhk2hIF0pDBGb73qSpUhCUx2AGg9XiBD2HcTvuu+QgOzdu9zPpUUKNJ6iIU HgaBcqF7fn1UQW2iyto1xvxVCYz6qM/M8kH2rzg8AhE+JDs1MJ3e+yoSe2mywpYB4pwyTQ Zbaz6rcKcBc6XXV/B2gcwQbxVVb2rC1waqQriDSsLNxfKXtkkqHZ3kKi+UQle+a9g6b5hO /eIre0/RU4gTBhDcSgR0J8F4Nj0OfgcBRfzKYNZH6tImmIgsRj/KsdzczAe2JPCayXcUFS qg19ztR+vFmcZz/zTX1QsFAUg8OF8/yJYn1mgkVqredlSHC2u2tB5pkEqxTlDM8s3ITemz vfluxUojK8S50Q4/eA3zptx3HVNYjRWP7ismDaDMOu1NNfWlS5/RDjCGCKJTypS/s1dvts w07cEiKvxM9fNsxZUVFHT8mavbzfIVYFtMX57kE7fe1DwGvAcVotIaUw6GHQ X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 22 Jun 2026 04:29:03 -0400 (EDT) Date: Mon, 22 Jun 2026 17:28:58 +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="/iYDm/a1PC/hXmGI" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --/iYDm/a1PC/hXmGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 21, 2026 at 07:51:25AM +0900, Michael Paquier wrote: > 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. 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=20 ABI file. Removing the entry in the same commit that adjusts the pgstats routine to be ABI-compatible should work, and there is no point in adding an extra entry to re-document the opposite ABI change. Any comments perhaps? -- Michael --/iYDm/a1PC/hXmGI Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmo48koACgkQnvQgOdby QH07nxAApVLOVIN6zvzZGMYJ0G366zgl1qjq27dh1gzAifMFAlO7QXdnf2BaOZug EoeamOgFZMsPctpC56UkVv+eXJO1zPOSGOSMRUwRBctmU4GqLw9xQl1TqV1hU/s+ wVAsKeUzyQ+PyxDb7pCT9ENQGjf+hJZUb37uGloNUQ5odEGqGdjDY7dYPM8c4jQ7 vF1d0EWw669XGqJ9pvTI8b4BlL2IILyePBCCau2N1xaF1PcBY4oMUe52U2BQSZXQ DU0+BGaXeJMCTtc9xqnMbJeLiLBqNfdaruueE+J3LOP12tL8aU1S1BYSq11oqNax tRGxi/7z7Ts/KbylMNUyS0I/y9XvpuWTw41ZaVHWocs19PIYEMApc+k00cgXDhDq lIJCUJkrSOP4LFswz8yXNd/ch+jz/nxsmOPZHv6UrCc8mV6zNzLoEJJb4l9VkjL0 UmmXkgmHeU1iM49jkrzRzKZnhoWnJdGOQnt6/Wahd+BR+R52dKO4+Fnmes3j/+5/ N4JB9KINK4H/qpFoTsXpyMr4wQXVund2UCLU4NJUXemb1UwTRZJ6r+AeyjRlAB1+ zk6Jw5th6aWDMlzHcRW1QDy95q4GUAeqs53ZbQie6asxrDHlIncfY/9U/MUX6Phb b3Eljngh09ZOFZEAoL8vtB92kI7UmP/8056KfrYXGKz0I6FB3+Y= =Ks2a -----END PGP SIGNATURE----- --/iYDm/a1PC/hXmGI--