Re: v7.1 error ... SELECT converted to a COPY? - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: v7.1 error ... SELECT converted to a COPY?
Date
Msg-id 3AEFD2E6.D221F706@tm.ee
Whole thread Raw
In response to Re: v7.1 error ... SELECT converted to a COPY?  (The Hermit Hacker <scrappy@hub.org>)
List pgsql-hackers
The Hermit Hacker wrote:
> 
> On Mon, 30 Apr 2001, Tom Lane wrote:
> 
> > The Hermit Hacker <scrappy@hub.org> writes:
> > > Okay, maybe this query isn't quite as simple as I think it is, but does
> > > this raise any flags for anyone?  How did I get into a COPY?  It appears
> > > re-creatable, as I've done it twice so far ...
> >
> > > eceb=# select e.idnumber,e.password from egi e, auth_info a where e.idnumber != a.idnumber;
> > > Backend sent D message without prior T
> > > Backend sent D message without prior T
> >
> > At a guess, you're running out of memory on the client side for the
> > SELECT results (did you really want a not-equal rather than equal
> > constraint there!?)
> 
> Yup, want to figure out which ones are in the egi table that I hadn't
> transfer'd over yet ... tried it with a NOT IN ( SELECT ... ) combination,
> but an explain of that showed two sequential searches on the tables,

did you do it as

select e.idnumber,e.password from egi ewhere e.idnumber not in (select idnumber from auth_info a where
e.idnumber = a.idnumber)
;

to smarten up the optimizer about using a join ?

I guess that it can be done using outer joins and testing the "outer2
part for IS NULL in 7.1

-------------------
Hannu


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Collation order for btree-indexable datatypes
Next
From: Alfred Perlstein
Date:
Subject: Re: New Linux xfs/reiser file systems