From: | "Tsukaeru(dot)net Webmaster" <webmaster(at)tsukaeru(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Backend message type 0x44 arrived while idle |
Date: | 2001-08-24 03:58:01 |
Message-ID: | 002901c12c51$0cda70e0$651ea8c0@tokyo.fnx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tsukaeru.net Webmaster" <webmaster(at)tsukaeru(dot)net>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Friday, August 24, 2001 12:31 PM
Subject: Re: [GENERAL] Backend message type 0x44 arrived while idle
> "Tsukaeru.net Webmaster" <webmaster(at)tsukaeru(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-08-24 04:30:11 | Re: Backend message type 0x44 arrived while idle |
Previous Message | Willis, Ian (Ento, Canberra) | 2001-08-24 03:56:42 | RE: SELECT FOR UPDATE |