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

From: naveenallin(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #14531: server process (PID 12714) was terminated by signal 11: Segmentation fault
Date: 2017-02-07 13:56:35
Message-ID: 20170207135635.1411.1311@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14531
Logged by: Naveen Chalmeti
Email address: naveenallin(at)gmail(dot)com
PostgreSQL version: 9.6.1
Operating system: Ubuntu 14.04.1 LTS
Description:

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.
During the crash we have got a system crash file and extracted to get the
back trace. Unluckily we are using postgres release binary using which we
cannot get the full pledged back trace.

Rough Backtrace:
gdb -se /usr/lib/postgresql/9.6/bin/postgres --core=CoreDump
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/postgresql/9.6/bin/postgres...(no debugging
symbols found)...done.
[New LWP 14138]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `postgres: 9.6/main: postgres Database
127.0.0.1(58814) SELECT '.
Program terminated with signal SIGSEGV, Segmentation fault.

(gdb) bt full
#0 0x00007fddcbc4e4ec in ExecClearTuple ()
No symbol table info available.
#1 0x00007fddcbc63fb8 in ExecEndSeqScan ()
No symbol table info available.
#2 0x00007fddcbc42f4c in standard_ExecutorEnd ()
No symbol table info available.
#3 0x00007fddcbc0d744 in PortalCleanup ()
No symbol table info available.
#4 0x00007fddcbe81c92 in PortalDrop ()
No symbol table info available.
#5 0x00007fddcbd5ee81 in PostgresMain ()
No symbol table info available.
#6 0x00007fddcbae43fb in ?? ()
No symbol table info available.
#7 0x00007fddcbcfe06b in PostmasterMain ()
No symbol table info available.
#8 0x00007fddcbae5142 in main ()
No symbol table info available.

As it is affecting our production environment please do help us quickly.

Thanks in advance.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message digoal 2017-02-07 15:04:20 BUG #14532: implict type case invalid in gin?
Previous Message CR VV 2017-02-07 12:56:00 Re: BUG #14524: Commands compare with nested subquery expressions fail with "should not reference subplan var"