Re: Segmentation fault when running queries in sequence

From: Matt Gibbins <matt_gibbins(at)fastmail(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Segmentation fault when running queries in sequence
Date: 2023-09-24 00:46:25
Message-ID: 94eaab7c-b764-418e-a623-c6b4911f4e32@fastmail.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 24/9/23 09:56, Tom Lane wrote:
> Matt Gibbins<matt_gibbins(at)fastmail(dot)com(dot)au> writes:
>> When I launch gdb for stack trace on the server the process hangs.
> If you mean you're attaching gdb to the active server process, yes
> that would stop execution. You could just say "continue" and
> wait for the segfault to occur.
>
> regards, tom lane

Tom

Thanks for that

I launched gdb on the server with sudo gdp -p <port>.

Launched the client on the remote connection then executed continue in
the gdb prompt on the server.

Initial response

Continuing.

Program received signal SIGUSR1, User defined signal 1.

I executed continue and the gdb reported '[Detaching after fork from
child process 2790431]' for several sequences and the remote process
then crashed.

No further information available other than 'Detaching after fork...'.

Regards

Matt.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2023-09-24 00:54:34 Re: Segmentation fault when running queries in sequence
Previous Message Matt Gibbins 2023-09-24 00:20:57 Re: Segmentation fault when running queries in sequence