Re: Bug #514: Backend crashes periodically

Tom,

Here ya go...

bt output:

#0 ExecEvalVar (variable=0x8239888, econtext=0x8239ed8,
isNull=0x823b7c4 "") at execQual.c:323
#1 0x80c1a2b in ExecEvalExpr (expression=0x8239888,
econtext=0x8239ed8, isNull=0x823b7c4 "", isDone=0xbfffea0c) at
execQual.c:1187
#2 0x80c1431 in ExecEvalFuncArgs (fcache=0x823b760,
argList=0x82398b0, econtext=0x8239ed8) at execQual.c:614
#3 0x80c14b0 in ExecMakeFunctionResult (fcache=0x823b760,
arguments=0x82398b0, econtext=0x8239ed8, isNull=0xbfffeadf "",
isDone=0x0) at execQual.c:667
#4 0x80c165e in ExecEvalOper (opClause=0x8239838,
econtext=0x8239ed8, isNull=0xbfffeadf "", isDone=0x0) at
execQual.c:859
#5 0x80c1aa0 in ExecEvalExpr (expression=0x8239838,
econtext=0x8239ed8, isNull=0xbfffeadf "", isDone=0x0) at
execQual.c:1222
#6 0x80c1bc6 in ExecQual (qual=0x8239908, econtext=0x8239ed8,
resultForNull=0 '\000') at execQual.c:1374
#7 0x80c56db in IndexNext (node=0x8238c98) at nodeIndexscan.c:133
#8 0x80c2063 in ExecScan (node=0x8238c98, accessMtd=0x80c55e0
<IndexNext>) at execScan.c:95
#9 0x80c58af in ExecIndexScan (node=0x8238c98) at nodeIndexscan.c:283
#10 0x80c0729 in ExecProcNode (node=0x8238c98, parent=0x8237d60) at
execProcnode.c:282
#11 0x80c724c in ExecNestLoop (node=0x8237d60) at nodeNestloop.c:165
#12 0x80c0759 in ExecProcNode (node=0x8237d60, parent=0x8237d60) at
execProcnode.c:297
#13 0x80c0392 in EvalPlanQualNext (estate=0x822ea18) at execMain.c:1884
#14 0x80c0369 in EvalPlanQual (estate=0x822ea18, rti=4,
tid=0xbfffed28) at execMain.c:1870
#15 0x80bfcbb in ExecReplace (slot=0x822f970, tupleid=0xbfffed98,
estate=0x822ea18) at execMain.c:1465
#16 0x80bf951 in ExecutePlan (estate=0x822ea18, plan=0x822df90,
operation=CMD_UPDATE, numberTuples=0, direction=ForwardScanDirection,
destfunc=0x82374e8)
at execMain.c:1125
#17 0x80bedb7 in ExecutorRun (queryDesc=0x822f640, estate=0x822ea18,
feature=3, count=0) at execMain.c:233
#18 0x8105ab3 in ProcessQuery (parsetree=0x820cf98, plan=0x822df90,
dest=Remote) at pquery.c:295
#19 0x81044d1 in pg_exec_query_string (query_string=0x820caa0 "DELETE
FROM session WHERE session_key =
'bRUjmnqcb5prUNRE.Bb0sq+fZB69dkdVlCAKNBsb'", dest=Remote,
parse_context=0x81e6d58) at postgres.c:810
#20 0x8105564 in PostgresMain (argc=4, argv=0xbffff050, real_argc=4,
real_argv=0xbffff9c4, username=0x81dcc09 "sis") at postgres.c:1908
#21 0x80f0194 in DoBackend (port=0x81dc9a0) at postmaster.c:2114
#22 0x80efd4c in BackendStartup (port=0x81dc9a0) at postmaster.c:1897
#23 0x80eef79 in ServerLoop () at postmaster.c:995
#24 0x80ee963 in PostmasterMain (argc=4, argv=0xbffff9c4) at postmaster.c:685
#25 0x80cefad in main (argc=4, argv=0xbffff9c4) at main.c:171
#26 0x400e92eb in __libc_start_main (main=0x80cee90 <main>, argc=4,
ubp_av=0xbffff9c4, init=0x80653ec <_init>, fini=0x8148c8c <_fini>,
rtld_fini=0x4000c130 <_dl_fini>, stack_end=0xbffff9bc) at
../sysdeps/generic/libc-start.c:129

p debug_query_string output:

$1 = 0x820caa0 "DELETE FROM session WHERE session_key =
'bRUjmnqcb5prUNRE.Bb0sq+fZB69dkdVlCAKNBsb'"

-Warren

>pgsql-bugs(at)postgresql(dot)org writes:
>> Program terminated with signal 11, Segmentation fault.
>> (Omitted symbol loading)
>> #0 ExecEvalVar (variable=0x8239888, econtext=0x8239ed8,
>>isNull=0x823b7c4 "") at execQual.c:323
>> 323 heapTuple = slot->val;
>
>This isn't enough to say anything useful, but please send the results of
> bt
>and
> p debug_query_string
>in this same corefile.