Re: Backend message type 0x44 arrived while idle - Mailing list pgsql-general

From Tsukaeru.net Webmaster
Subject Re: Backend message type 0x44 arrived while idle
Date
Msg-id 002901c12c51$0cda70e0$651ea8c0@tokyo.fnx.com
Whole thread Raw
In response to Backend message type 0x44 arrived while idle  ("Tsukaeru.net Webmaster" <webmaster@tsukaeru.net>)
Responses Re: Backend message type 0x44 arrived while idle  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I can actually select just one row as

select  * from table limit 1 offset 270
(anything below 270 is fine)

and the same error pops up. It have heaps of memory available..

Jason

----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Tsukaeru.net Webmaster" <webmaster@tsukaeru.net>
Cc: <pgsql-general@postgresql.org>
Sent: Friday, August 24, 2001 12:31 PM
Subject: Re: [GENERAL] Backend message type 0x44 arrived while idle


> "Tsukaeru.net Webmaster" <webmaster@tsukaeru.net> writes:
> > My database is giving me trouble. I assume that it is due to a bad
record,
> > but I am unable to select/delete that record. Have checked logs with no
> > helpful info.
>
> The problem could be at the client side, eg libpq running out of memory.
> (Its recovery from this problem is pretty abysmal at the moment :-(.)
> Are you selecting a whole lot of data in this query?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl
>


pgsql-general by date:

Previous
From: "Willis, Ian (Ento, Canberra)"
Date:
Subject: RE: SELECT FOR UPDATE
Next
From: Tom Lane
Date:
Subject: Re: Backend message type 0x44 arrived while idle