[BUGS] BUG #14781: server process was terminated by signal 11: Segmentationfault - Mailing list pgsql-bugs

From maksim_karaba@epam.com
Subject [BUGS] BUG #14781: server process was terminated by signal 11: Segmentationfault
Date
Msg-id 20170816113206.27368.44100@wrigleys.postgresql.org
Whole thread Raw
Responses Re: [BUGS] BUG #14781: server process was terminated by signal 11: Segmentation fault
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      14781
Logged by:          Maksim Karaba
Email address:      maksim_karaba@epam.com
PostgreSQL version: 9.6.4
Operating system:   CentOS Linux release 7.3.1611 (Core)
Description:

Hi!
We are getting error "server process was terminated by signal 11:
Segmentation fault" and server goes to recovery mode on production system.
It repeats several times a day, always on complicated updates using
postgres_fdw. Could you provide any workaround? Version Postgresql 9.6.4
Error from /var/log/messages :
bigdatadb kernel: postgres[17467]: segfault at 58 ip 00000000005c2f94 sp
00007ffdc06b2260 error 4 in postgres[400000+616000]
bigdatadb abrt-hook-ccpp: Process 17467 (postgres) of user 26 killed by
SIGSEGV - dumping core

And we have core dump bt list:

#0  ExecProcNode (node=0x0) at execProcnode.c:380       result = <optimized out>       __func__ = "ExecProcNode"
#1  0x00007f534be36554 in postgresRecheckForeignScan (node=<optimized out>,
slot=0x6afbf68) at postgres_fdw.c:2059       scanrelid = <optimized out>       outerPlan = <optimized out>       result
=<optimized out>
 
#2  0x00000000005e3b7c in ForeignRecheck (node=node@entry=0x6afba48,
slot=slot@entry=0x6afbf68) at nodeForeignscan.c:101       fdwroutine = 0x6a48b88       econtext = 0x6afbb58
#3  0x00000000005ca5a6 in ExecScanFetch (recheckMtd=0x5e3b40
<ForeignRecheck>, accessMtd=0x5e3bb0 <ForeignNext>, node=0x6afba48) at
execScan.c:85       slot = <optimized out>       scanrelid = <optimized out>       estate = <optimized out>
#4  ExecScan (node=node@entry=0x6afba48, accessMtd=accessMtd@entry=0x5e3bb0
<ForeignNext>, recheckMtd=recheckMtd@entry=0x5e3b40 <ForeignRecheck>) at
execScan.c:180       econtext = 0x6afbb58       qual = 0x0       projInfo = 0x6afc0d0       isDone = ExprSingleResult
   resultSlot = <optimized out>
 
#5  0x00000000005e3c5f in ExecForeignScan (node=node@entry=0x6afba48) at
nodeForeignscan.c:119
No locals.
#6  0x00000000005c36a8 in ExecProcNode (node=node@entry=0x6afba48) at
execProcnode.c:465       result = <optimized out>       __func__ = "ExecProcNode"
#7  0x00000000005e0889 in ExecSort (node=node@entry=0x6afb7d8) at
nodeSort.c:103       plannode = <optimized out>       outerNode = 0x6afba48       tupDesc = <optimized out>
estate= 0x6a42dc8       dir = ForwardScanDirection       tuplesortstate = 0x6b70868       slot = <optimized out>
 
#8  0x00000000005c3648 in ExecProcNode (node=node@entry=0x6afb7d8) at
execProcnode.c:495       result = <optimized out>       __func__ = "ExecProcNode"
#9  0x00000000005e448e in begin_partition
(winstate=winstate@entry=0x6a50b28) at nodeWindowAgg.c:1082       outerslot = <optimized out>       outerPlan =
0x6afb7d8      numfuncs = 1       i = <optimized out>
 
#10 0x00000000005e6a4b in ExecWindowAgg (winstate=winstate@entry=0x6a50b28)
at nodeWindowAgg.c:1691       result = <optimized out>       isDone = ExprSingleResult       econtext = <optimized out>
     i = <optimized out>       numfuncs = <optimized out>       __func__ = "ExecWindowAgg"
 
#11 0x00000000005c3618 in ExecProcNode (node=0x6a50b28) at
execProcnode.c:507

Thank you!


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: "Augustine, Jobin"
Date:
Subject: Re: [HACKERS] [BUGS] Replication to Postgres 10 on Windows is broken
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] [BUGS] [postgresql 10 beta3] unrecognized node type: 90