| From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Segmentation fault with PG-12 |
| Date: | 2019-10-08 18:40:13 |
| Message-ID: | VisenaEmail.11f.58514559296fe1e1.16dacaab834@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. Nice,
I'm using the ubuntu-packages, so I'll go ahead and installpostgresql-12-dbgsym
> 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
I'll look into that, 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>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2019-10-08 20:46:36 | Re: Declarative Range Partitioning Postgres 11 |
| Previous Message | Shatamjeev Dewan | 2019-10-08 18:14:15 | RE: Declarative Range Partitioning Postgres 11 |