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

From Andreas Joseph Krogh
Subject Segmentation fault with PG-12
Date
Msg-id VisenaEmail.112.19e4492494617f72.16dabe975f8@tc7-visena
Whole thread Raw
Responses Re: Segmentation fault with PG-12
List 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 by signal 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
Attachment

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Table locking during backup
Next
From: Tom Lane
Date:
Subject: Re: Segmentation fault with PG-12