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-25 12:00:50 |
Message-ID: | 00a301c12d5d$96821340$0200a8c0@earl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ok, have tried this in debug mode and the log shows....
010825.20:54:27.635 [8851] StartTransactionCommand
010825.20:54:27.635 [8851] query: select * from users;
010825.20:54:27.645 [8851] ProcessQuery
Server process (pid 8851) exited with status 11 at Sat Aug 25 20:54:27 2001
Terminating any active server processes...
Server processes were terminated at Sat Aug 25 20:54:27 2001
Reinitializing shared memory and semaphores
010825.20:54:27.885 [8873] DEBUG: Data Base System is starting up at Sat
Aug 25 20:54:27 2001
Does this help at all?
Regards,
Jason Frisch
----- Original Message -----
From: "Tsukaeru.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>
Sent: Friday, August 24, 2001 12:58 PM
Subject: Re: [GENERAL] Backend message type 0x44 arrived while idle
> 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
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantinos Agouros | 2001-08-25 14:11:22 | Stupid foreign key question |
Previous Message | Peter Eisentraut | 2001-08-25 10:16:16 | Re: Error reporting when hitting shared memory limits - |