Jeff Eckermann <[EMAIL PROTECTED]> writes: > I was expecting not much more than 50 rows to be returned, with an absolute > maximum of 70. > I was trying to simulate an outer join by using the "where not exists" > clause, so that I would get back my full list of 70 and be able to see the > unmatched entries... Certainly 70 rows are not going to strain memory ;-). My guess is that the query didn't do what you thought, but instead produced some sort of cross-product result... regards, tom lane
- RE: [GENERAL] Query bombed: why? Jeff Eckermann
- Tom Lane