Re: Segmentation fault with PG-12

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Segmentation fault with PG-12
Date: 2019-10-09 11:21:20
Message-ID: VisenaEmail.88.9118db0ab9c48d81.16db03f0c72@tc7-visena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

På tirsdag 08. oktober 2019 kl. 17:24:21, skrev Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
<mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>>: Andreas Joseph Krogh <andreas(at)visena(dot)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 andreas(at)visena(dot)com
<mailto:andreas(at)visena(dot)com> www.visena.com <https://www.visena.com>
<https://www.visena.com>

Attachment Content-Type Size
gdb.txt text/plain 16.9 KB

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Luca Ferrari 2019-10-09 12:02:52 Re: Event Triggers and Dropping Objects
Previous Message Allan Jensen 2019-10-09 08:49:34 GSSAPI: logging principal