From: Matt Gibbins <matt_gibbins@fastmail.com.au>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Segmentation fault when running queries in sequence
Date: Sun, 24 Sep 2023 12:50:14 +1000
Message-ID: <4fbf8190-92f7-4272-8b71-3bc2f8029e71@fastmail.com.au> (raw)
In-Reply-To: <1430983.1695516874@sss.pgh.pa.us>
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>
<1430983.1695516874@sss.pgh.pa.us>
On 24/9/23 10:54, Tom Lane wrote:
> 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
Tom
Thank you for your patience.
I have now created a core dump of the process. It is approximately 4G in
size.
Rather large for an email.
As I am not familiar with core dump processing I require some further
guidance.
Matt.
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: matt_gibbins@fastmail.com.au, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
Subject: Re: Segmentation fault when running queries in sequence
In-Reply-To: <4fbf8190-92f7-4272-8b71-3bc2f8029e71@fastmail.com.au>
* 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