Skip site navigation (1) Skip section navigation (2)

Re: BUG #5238: frequent signal 11 segfaults

From: Nagy Daniel <nagy(dot)daniel(at)telekom(dot)hu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, "pgsql-bugs(at)postgresql(dot)org"<pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5238: frequent signal 11 segfaults
Date: 2009-12-12 21:26:22
Message-ID: 4B240A7E.3030009@telekom.hu (view raw or flat)
Thread:
Lists: pgsql-bugs
Here's a better backtrace:

(gdb) bt
#0  slot_deform_tuple (slot=0xc325b8, natts=21) at heaptuple.c:1130
#1  0x00000000004535f0 in slot_getsomeattrs (slot=0xc325b8, attnum=21)
at heaptuple.c:1340
#2  0x0000000000543cc6 in ExecProject (projInfo=0xc44c98,
isDone=0x7fffe33f30a4) at execQual.c:5164
#3  0x00000000005528fb in ExecHashJoin (node=0xc3f130) at nodeHashjoin.c:282
#4  0x0000000000543368 in ExecProcNode (node=0xc3f130) at execProcnode.c:412
#5  0x0000000000552aa6 in ExecHashJoin (node=0xc3dc90) at nodeHashjoin.c:598
#6  0x0000000000543368 in ExecProcNode (node=0xc3dc90) at execProcnode.c:412
#7  0x0000000000552aa6 in ExecHashJoin (node=0xc37140) at nodeHashjoin.c:598
#8  0x0000000000543368 in ExecProcNode (node=0xc37140) at execProcnode.c:412
#9  0x0000000000557251 in ExecSort (node=0xc37030) at nodeSort.c:102
#10 0x0000000000543290 in ExecProcNode (node=0xc37030) at execProcnode.c:423
#11 0x0000000000555308 in ExecMergeJoin (node=0xc36220) at
nodeMergejoin.c:626
#12 0x0000000000543380 in ExecProcNode (node=0xc36220) at execProcnode.c:408
#13 0x0000000000557251 in ExecSort (node=0xc34000) at nodeSort.c:102
#14 0x0000000000543290 in ExecProcNode (node=0xc34000) at execProcnode.c:423
#15 0x0000000000540e92 in standard_ExecutorRun (queryDesc=0xbc1c10,
direction=ForwardScanDirection, count=0) at execMain.c:1504
#16 0x00000000005ecc27 in PortalRunSelect (portal=0xc30160,
forward=<value optimized out>, count=0, dest=0x7f7219b7f3e8)
    at pquery.c:953
#17 0x00000000005edfd9 in PortalRun (portal=0xc30160,
count=9223372036854775807, isTopLevel=1 '\001', dest=0x7f7219b7f3e8,
    altdest=0x7f7219b7f3e8, completionTag=0x7fffe33f3620 "") at pquery.c:779
#18 0x00000000005e93a7 in exec_simple_query (
    query_string=0xb89a00 "SELECT w1.kivel, date_max(w1.mikor,w2.mikor),
w1.megnezes, u.* FROM valogatas_valasz w1, valogatas_valasz w2, useradat
u WHERE w1.ki=65549 AND not w1.del AND w2.kivel=65549 AND w1.megnezes=0
AND w1.ki"...) at postgres.c:991
#19 0x00000000005ea977 in PostgresMain (argc=4, argv=<value optimized
out>, username=0xaceb10 "randir") at postgres.c:3614
#20 0x00000000005bf2a8 in ServerLoop () at postmaster.c:3447
#21 0x00000000005c0037 in PostmasterMain (argc=3, argv=0xac9820) at
postmaster.c:1040
#22 0x0000000000569b48 in main (argc=3, argv=0xac9820) at main.c:188

(gdb) p debug_query_string
$1 = 0xb89a00 "SELECT w1.kivel, date_max(w1.mikor,w2.mikor),
w1.megnezes, u.* FROM valogatas_valasz w1, valogatas_valasz w2, useradat
u WHERE w1.ki=65549 AND not w1.del AND w2.kivel=65549 AND w1.megnezes=0
AND w1.ki"...


Thanks,

Daniel



Tom Lane wrote:
> Nagy Daniel <nagy(dot)daniel(at)telekom(dot)hu> writes:
>> (gdb) p debug_query_string
>> $1 = 12099472
> 
> Huh, your stripped build is being quite unhelpful :-(.  I think
> "p (char *) debug_query_string" would have produced something useful.
> 
> 			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-12-13 03:13:05
Subject: Re: BUG #5238: frequent signal 11 segfaults
Previous:From: Tom LaneDate: 2009-12-12 19:29:51
Subject: Re: BUG #5238: frequent signal 11 segfaults

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group