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 1nqcXZ-00033c-BY for pgsql-bugs@arkaria.postgresql.org; Mon, 16 May 2022 15:21:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nqcXX-0004t5-OV for pgsql-bugs@arkaria.postgresql.org; Mon, 16 May 2022 15:21:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nqcXX-0004qr-Gl for pgsql-bugs@lists.postgresql.org; Mon, 16 May 2022 15:21:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nqcXV-0003Fm-Eo for pgsql-bugs@lists.postgresql.org; Mon, 16 May 2022 15:21:43 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 24GFLLvE1371139; Mon, 16 May 2022 11:21:21 -0400 From: Tom Lane To: mailtch@163.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17481: sometime pg_stat_statements coredump In-reply-to: <17481-953591f62b3f8a58@postgresql.org> References: <17481-953591f62b3f8a58@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Sun, 15 May 2022 02:37:22 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1371137.1652714481.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 16 May 2022 11:21:21 -0400 Message-ID: <1371138.1652714481@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > In my database , use pg_stat_statement, but sometime, coredump > occurred,Details are as follows: 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. regards, tom lane