Re: Backend sent D message without prior T

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: Backend sent D message without prior T
Date: 2001-04-14 07:59:31
Message-ID: 13437.987235171@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jeff Eckermann <jeff(at)akira(dot)eckermann(dot)com> writes:
> Based on past posts I have read, this error is usually associated with
> running out of memory for the query result. Problem is, I am only
> expecting about 30 lines of moderate length to be returned....

Have you verified that by doing
select count(*) from ... where ...
Watching psql's memory usage with top(1) is another way to check whether
a memory overrun might be happening.

The 'D message without prior T' followed by unexpected switch into COPY
mode certainly suggests that libpq has lost sync with the backend's
output. I am not aware of any failure modes that cause that in 7.0.3,
other than the aforementioned out-of-memory problem.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-04-14 08:08:14 Re: Order in CREATE VIEW
Previous Message will trillich 2001-04-14 07:21:10 Re: Help on PGSQL