Hi Tom,
I've upgraded to 7.3.2 and the problem still exists :(. I'm not that
familiar with the workings of GDB but I managed to get a backtrace for
you:
(gdb) continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x0811ed8c in BufFileWrite ()
(gdb) bt
#0 0x0811ed8c in BufFileWrite ()
#1 0x080dc237 in ExecHashJoinSaveTuple ()
#2 0x080db201 in ExecHash ()
#3 0x080d5f6d in ExecProcNode ()
#4 0x080dbb06 in ExecHashJoin ()
#5 0x080d5f7d in ExecProcNode ()
#6 0x080d4d44 in ExecutePlan ()
#7 0x080d4389 in ExecutorRun ()
#8 0x081294fb in ProcessQuery ()
#9 0x081279bb in pg_exec_query_string ()
#10 0x08128ad3 in PostgresMain ()
#11 0x0810f044 in DoBackend ()
#12 0x0810e92d in BackendStartup ()
#13 0x0810d9c0 in ServerLoop ()
#14 0x0810d3f9 in PostmasterMain ()
#15 0x080e8cdd in main ()
#16 0x42017499 in __libc_start_main () from /lib/i686/libc.so.6
(gdb)
You may be on the right track with your overflow theory - we estimate
that the query should return somewhere in the region of 29M records as
this is one of the largest layers we have in the DB. Please let me know
if you need any more information and I will do my best to help.
Cheers,
Mark.
---
Mark Cave-Ayland
Webbased Ltd.
Tamar Science Park
Derriford
Plymouth
PL6 8BX
England
Tel: +44 (0)1752 764445
Fax: +44 (0)1752 764446
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender. You
should not copy it or use it for any purpose nor disclose or distribute
its contents to any other person.