Fw: [BUGS] BUG #1015: Got a signal 11 while trying to create a temp table

[aarjan langereis]

I tried to reply to you but that doesn't work. So I try it through here..   Yours,   Aarjan ----- Original Message ----- From: aarjan langereis To: Tom Lane Sent: Saturday, December 20, 2003 3:17 PM Subject: Fw: [BUGS] BUG #1015: Got a signal 11 while trying to create a temp table Did you find time to read my email? I hope you will reply sone.   Yours,   Aarjan   ----- Original Message ----- From: aarjan langereis To: [EMAIL PROTECTED] Sent: Friday, December 19, 2003 9:39 AM Subject: Re: [BUGS] BUG #1015: Got a signal 11 while trying to create a temp table How do I get a "debugger backtrace" ? Selecting all data from the tables involved, does that also include a 'count(*)', if so, they work: stats=# select count(*) from blocks;   count ---------  3194409 (1 row) stats=# select count(*) from hosts;  count -------    205 (1 row) stats=# Yours, Aarjan ----- Original Message ----- From: "Tom Lane" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "PostgreSQL Bugs List" <[EMAIL PROTECTED]> Sent: Friday, December 19, 2003 4:41 AM Subject: Re: [BUGS] BUG #1015: Got a signal 11 while trying to create a temp table > "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > > I tried to create a temp table and got my back-end restarting because of a signal 11. > > Hmm.  Can you get a debugger backtrace from the core dump? > > > It seems to me, and please correct me if Iā?Tm wrong, that there is a limit to the size that a join can handle. > > No (and certainly not on a measly 3-million-row case).  This could be a > data corruption problem, or something more subtle, but it's not that. > > One way of testing the data-corruption theory is to see if you can > select all the data from the tables involved, without any join. > > regards, tom lane >