From: Tom Lane <tgl@sss.pgh.pa.us>
To: mailtch@163.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17481: sometime pg_stat_statements coredump
Date: Mon, 16 May 2022 11:21:21 -0400
Message-ID: <1371138.1652714481@sss.pgh.pa.us> (raw)
In-Reply-To: <17481-953591f62b3f8a58@postgresql.org>
References: <17481-953591f62b3f8a58@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, mailtch@163.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17481: sometime pg_stat_statements coredump
In-Reply-To: <1371138.1652714481@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox