Re: BUG #14531: server process (PID 12714) was terminated by signal 11: Segmentation fault

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: naveenallin(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14531: server process (PID 12714) was terminated by signal 11: Segmentation fault
Date: 2017-02-07 16:09:26
Message-ID: 15863.1486483766@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

naveenallin(at)gmail(dot)com writes:
> We are facing frequent crash issue in postgresql due to segmentation fault.
> We have tried various ways to debug the issue such as enabling debug level
> log etc., but we could not get any idea what is the reason behind the crash.

The postmaster should at least have logged what statement a crashed
backend was running (assuming you've not disabled the statistics
subsystem). Is there any consistency to that? It might be worth
turning on full statement logging (log_statement=all) so that you
can see everything the crashed sessions did.

The backtrace you show doesn't look much like any known 9.6 bug,
so we'd be very interested if you can put together a reproducible
test case.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-02-07 16:26:07 Re: BUG #14532: implict type case invalid in gin?
Previous Message gustavfc.freitas 2017-02-07 15:05:54 BUG #14533: PgAdmin 4 v1 crash