(gdb) p debug_query_string $1 = 12099472 Now I recompiled pg with --enable-debug and waiting for a new core dump. I'll post the backtrace and the debug_query_string output ASAP.
Please let me know if there is anything more I can do. Thanks, Daniel Tom Lane wrote: > Nagy Daniel <nagy.dan...@telekom.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
