Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nqkWW-0004Ct-AO for pgsql-bugs@arkaria.postgresql.org; Mon, 16 May 2022 23:53:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nqkWV-0007u6-5q for pgsql-bugs@arkaria.postgresql.org; Mon, 16 May 2022 23:53:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nqkWT-0007tv-Ie for pgsql-bugs@lists.postgresql.org; Mon, 16 May 2022 23:53:10 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nqkWQ-0004Sz-Ek for pgsql-bugs@lists.postgresql.org; Mon, 16 May 2022 23:53:08 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 87D1932009B2; Mon, 16 May 2022 19:53:03 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 16 May 2022 19:53:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1652745183; x=1652831583; bh=YDxZb922NE RDGk0kkWpDCsavRtfGbXuTwAjj2tOpR2c=; b=V40iF14ffMie6JG7/l7EH6+U74 EpkDvDzZwQ8U2RIv1Xqyqlcm9SwbOO2WJXi9aT6zLfa+A3OAU4TxAPCtfKC4llr6 Ax4vEYAEujpUbVig84np5QUj7eUHj20ES7X0iCzcZtR4p1HxenSETFqRRYWfyuKu Dup1ufu69d7pSnZabTOUJkT2hMJjUDEOrbyKNCeIRzUecOW812XLmOEGlbxMTuU9 d+XtFgGetbU4sJF/24CT2gy88HcDV5s4fUQhkZMVgsOuRhzNRm8kNYh4KD/Q7UOw pxTOOmpRr55KvHLem8kBoUbyDC7Cff8/kSFSMnCrhFZdKW0X7mJLaPk+0UYA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1652745183; x= 1652831583; bh=YDxZb922NERDGk0kkWpDCsavRtfGbXuTwAjj2tOpR2c=; b=k ovLIr6ex5AsG4ZxFTHNdzp0eGVqX/rcCNFlDweUripaNv5JfhdooZzfkoEScPl6q /4uZ7nR9SHpqMh2uUokRp/w2xpgmedoOSiMjBLg2aRByCvh+mB70o33tLqcCHcBA oYtBshwPEYhHcRtqDfgV/tXHBOmRtQLTshYUk6ZRYRCXZtyZWeLbDxFszTQjnVaj 0gE6bEdh1ptOwnzjwDhfkkWMvQRdmpQSuIiCesAXfbT0SLOdTo6/BNS0Irj64OfR JureK5lhabGDiaqGavvroWhuTVW5OiWzFR6cc2ekou5FLPNNa7Wc6u39OQ59z78N ZuR87/CV4916Iq0Fa0vig== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrheeigddvjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdejtddmnecujfgurhepfffhvf evuffkfhggtggujgesghdtreertddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhu ihgvrhcuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenucggtffrrghtthgvrh hnpeetleeifedufffhhfdtteelgeeggeffhfekueevteeigfduudevudetgfegiedvjeen ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthh grvghlsehprghquhhivghrrdighiii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 16 May 2022 19:53:01 -0400 (EDT) Date: Tue, 17 May 2022 08:52:57 +0900 From: Michael Paquier To: Tom Lane Cc: mailtch@163.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17481: sometime pg_stat_statements coredump Message-ID: References: <17481-953591f62b3f8a58@postgresql.org> <1371138.1652714481@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="lCxNMj4Um/qaaMKz" Content-Disposition: inline In-Reply-To: <1371138.1652714481@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --lCxNMj4Um/qaaMKz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, May 16, 2022 at 11:21:21AM -0400, Tom Lane wrote: > Not much info here. Can you install the debug symbols for the postgres > package you're using and repeat the backtrace? Another potentially useful > bit of info would be the source text for the query that's causing the > failure, which you could get with "p debug_query_string" in gdb. CleanQuerytext() would crash on a NULL string AFAIK, but this really smells like a case where a utility code path is freeing the pointer of the query string that PGSS is attempting to look at. I have seen this problem in the past, where this subtle issue could be created even if the code was rather careful in the query string handling. Here, are we dealing with a CALL that involves plpgsql? Or is that a different language, like something out of core? -- Michael --lCxNMj4Um/qaaMKz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmKC49kACgkQnvQgOdby QH1maRAAn3vJqXOdrxvDLxEyDOCrrzZr++p4YmKwy3/3COpGx3LC+YaO+/7IeJC/ PRIDNLjoOlH6C8XKOBYMmWbfcxw0U6wjncWeKlYGCYzYo546p3rnxSOCJdSm10TO v5KK+uuk+GoeIzO34+oFh8XZUOSm2ArdON2P+fWxV9ofeidSPKkE0Mr5DAwo4xjc LurAVxopTlETQUjtv1zguxTC41eUnThX3rxTxs1w2CD5Asz7tPoEMrxXy47tq9tC 5zw/bi5E++zORdet76GmW1OO/Hftk7PqMljacfH60pJWuKLq1YZsdek1bOsksaHw qp/5+tQz6vESvuvJpT2+glinmZDR89g0QIPFV1L9g3QoNrdlaxvfFRHF06/q8Fvd dWXwro6a30v7OV5AAo+Z0c1QlsyNQ5+/bghhpJnabS05CiAzMM0huepZ+A0XGIYv /vriQdT/ilqTAaPhKsWPYT6F4D0k6MT+3z7EJ6oY7Iay3ss5Oq7NfD5D59Q+x3ik vbakfZaSCwHUIuZN6Pj4IAd8RRu1Iz0ippleXL7b3Jv1ypb3OzLvuNK30WcDRzry MUhE40f9FBGf3TfPmG4zKRii9dBRjtMDqxvFmalVpqTGS3Mvlyrl8QPcTTs3FLbj EWewzUCmadTfwSIqdtzOKr7A07tXraztZSYMidxiLeNrtFqtMpQ= =6yNS -----END PGP SIGNATURE----- --lCxNMj4Um/qaaMKz--