| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | NAVEEN CHALIMETI <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 20:30:28 |
| Message-ID: | 21590.1486499428@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
NAVEEN CHALIMETI <naveenallin(at)gmail(dot)com> writes:
> Thanks for your reply firstly.
> I did not mention anything about logs thinking the back trace would be
> enough to solve the issue. Sorry for that.
> I have enabled the *log_statement=all* already and each time it gives
> different queries. But until now i have seen postmaster crashed during
> SELECT query.
> ...
> The crash is reproducible with different queries.
Hm. Have you looked at more than one core dump? Is it always the same
backtrace?
Those queries don't look particularly exciting, so I'm now thinking the
problem is something unusual. Do you have any nondefault extensions
installed? Maybe you built the server with some unusual options?
I dislike blaming hardware problems, but we shouldn't rule out that
possibility either, unless you're seeing this on more than one machine.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-02-07 20:44:07 | Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT |
| Previous Message | Peter Geoghegan | 2017-02-07 19:34:09 | Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT |