Re: Query bombed: why?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Eckermann <jeckermann(at)verio(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Query bombed: why?
Date: 2000-05-09 23:40:27
Message-ID: 15953.957915627@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jeff Eckermann <jeckermann(at)verio(dot)net> 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Hitesh Patel 2000-05-09 23:53:31 textpos() function
Previous Message Jeff Eckermann 2000-05-09 23:12:53 RE: Query bombed: why?