Received: from sss.pgh.pa.us (sss.pgh.pa.us [216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3U4sZ358212 for ; Mon, 30 Apr 2001 00:54:35 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f3U4sUR10467; Mon, 30 Apr 2001 00:54:30 -0400 (EDT) To: The Hermit Hacker cc: pgsql-hackers@postgresql.org Subject: Re: v7.1 error ... SELECT converted to a COPY? In-reply-to: References: Comments: In-reply-to The Hermit Hacker message dated "Mon, 30 Apr 2001 01:37:15 -0300" Date: Mon, 30 Apr 2001 00:54:30 -0400 Message-ID: <10464.988606470@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/1039 X-Sequence-Number: 8077 The Hermit Hacker 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!?) --- libpq tends not to cope with this too gracefully. Someone oughta fix that... regards, tom lane