From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matt Gibbins <matt_gibbins@fastmail.com.au>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Segmentation fault when running queries in sequence
Date: Sat, 23 Sep 2023 20:54:34 -0400
Message-ID: <1430983.1695516874@sss.pgh.pa.us> (raw)
In-Reply-To: <94eaab7c-b764-418e-a623-c6b4911f4e32@fastmail.com.au>
References: <728d1797-efdd-4298-8ab2-042a28ddaae2@fastmail.com.au>
<1282819.1695479196@sss.pgh.pa.us>
<a1ca0600-4dd5-49c7-aad0-24b6b4fcd410@fastmail.com.au>
<1418006.1695513406@sss.pgh.pa.us>
<94eaab7c-b764-418e-a623-c6b4911f4e32@fastmail.com.au>
Matt Gibbins <matt_gibbins@fastmail.com.au> writes:
> I executed continue and the gdb reported '[Detaching after fork from
> child process 2790431]' for several sequences and the remote process
> then crashed.
I think this means that you attached to the parent postmaster
process, not to the per-session child process where the crash
will occur.
On the whole, attaching to a live server process is kind of the
hard way to do this anyhow. I'd recommend enabling saving of
core dump files and then gdb'ing the core file. That avoids
needing to identify in advance the process that is going to crash.
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, matt_gibbins@fastmail.com.au, pgsql-admin@lists.postgresql.org
Subject: Re: Segmentation fault when running queries in sequence
In-Reply-To: <1430983.1695516874@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