Re: Segmentation fault with PG-12 - Mailing list pgsql-general

From Andreas Joseph Krogh
Subject Re: Segmentation fault with PG-12
Date
Msg-id VisenaEmail.88.9118db0ab9c48d81.16db03f0c72@tc7-visena
Whole thread Raw
In response to Re: Segmentation fault with PG-12  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Segmentation fault with PG-12
List pgsql-general
På tirsdag 08. oktober 2019 kl. 17:24:21, skrev Tom Lane <tgl@sss.pgh.pa.us>:
Andreas Joseph Krogh <andreas@visena.com> writes:
> Will running a debug-enabled build slow things noticably down?

gcc promises that the generated code is the same with or without debug.
I think clang does too.  With other compilers you may pay some penalty.

> Is there a way
> to make it dump a stack-trace (or back-trace in C-land?) on sig11?

You should be able to get a core file from which you can extract a
stack trace (and other info) after the fact.

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

regards, tom lane
 
Attached is output from "bt full".
 
Is this helpful?
Anything else I can do to help narrowing down the problem?
 
Thanks.
 
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
 
Attachment

pgsql-general by date:

Previous
From: Allan Jensen
Date:
Subject: GSSAPI: logging principal
Next
From: Luca Ferrari
Date:
Subject: Re: Event Triggers and Dropping Objects