Re: BUG #5238: frequent signal 11 segfaults

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nagy Daniel <nagy(dot)daniel(at)telekom(dot)hu>
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 15:12:19
Message-ID: 5390.1260630739@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Nagy Daniel <nagy(dot)daniel(at)telekom(dot)hu> writes:
> (gdb) backtrace
> #0 0x0000000000453415 in slot_deform_tuple ()
> #1 0x000000000045383a in slot_getattr ()
> #2 0x0000000000550dac in ExecHashGetHashValue ()
> #3 0x0000000000552a98 in ExecHashJoin ()
> #4 0x0000000000543368 in ExecProcNode ()
> #5 0x0000000000552aa6 in ExecHashJoin ()
> #6 0x0000000000543368 in ExecProcNode ()

Not terribly informative (these binaries are apparently not as
un-stripped as you thought). However, this suggests it's a specific
query going wrong --- "p debug_query_string" in gdb might tell you what.
Please see if you can extract a test case.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Roman Kononov 2009-12-12 16:59:47 Re: BUG #5237: strange int->bit and bit->int conversions
Previous Message Nagy Daniel 2009-12-12 09:41:55 Re: BUG #5238: frequent signal 11 segfaults