From: Tom Lane <tgl@sss.pgh.pa.us>
To: The Hermit Hacker <scrappy@hub.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: v7.1 error ... SELECT converted to a COPY?
Date: Mon, 30 Apr 2001 00:54:30 -0400
Message-ID: <10464.988606470@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.33.0104300134270.411-100000@mobile.hub.org>
References: <Pine.BSF.4.33.0104300134270.411-100000@mobile.hub.org>
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!?) --- libpq tends not to cope with this too
gracefully. Someone oughta fix that...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, scrappy@hub.org
Subject: Re: v7.1 error ... SELECT converted to a COPY?
In-Reply-To: <10464.988606470@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox