Segmentation fault with PG-12

From: Andreas Joseph Krogh <andreas(at)visena(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Segmentation fault with PG-12
Date: 2019-10-08 15:15:09
Message-ID: VisenaEmail.112.19e4492494617f72.16dabe975f8@tc7-visena
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In our production-environment we get sig11 every now and then after upgrading
to PG-12: 2019-10-08 15:45:29.654 CEST [8829-76] LOG: server process (PID
20631) was terminated bysignal 11: Segmentation fault
2019-10-08 15:45:29.654 CEST [8829-77] DETAIL: Failed process was running:
COMMIT
2019-10-08 15:45:29.654 CEST [8829-78] LOG: terminating any other active
server processes
Will running a debug-enabled build slow things noticably down? Is there a way
to make it dump a stack-trace (or back-trace in C-land?) on sig11? -- 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>

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2019-10-08 15:24:21 Re: Segmentation fault with PG-12
Previous Message Tom Lane 2019-10-08 15:02:31 Re: Table locking during backup