Thread: Backend message type 0x44 arrived while idle
Hi. 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. Version 7.0.2 on Cobalt RAQ4. Can anybody help? Jason
----- Original Message ----- From: "Tsukaeru.net Webmaster" <webmaster@tsukaeru.net> To: <pgsql-general@postgresql.org> Sent: Friday, August 24, 2001 10:33 AM Subject: [GENERAL] Backend message type 0x44 arrived while idle > Hi. > > 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. > > Version 7.0.2 on Cobalt RAQ4. > > Can anybody help? > > Jason > > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org >
Sorry forgot to send the whole message...
Backend message type 0x44 arrived while idle
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
Hope someone can help...
Jason
----- Original Message -----
From: "Tsukaeru.net Webmaster" <webmaster@tsukaeru.net>
To: <pgsql-general@postgresql.org>
Sent: Friday, August 24, 2001 10:33 AM
Subject: [GENERAL] Backend message type 0x44 arrived while idle
> Hi.
>
> 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.
>
> Version 7.0.2 on Cobalt RAQ4.
>
> Can anybody help?
>
> Jason
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
"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
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 >
"Tsukaeru.net Webmaster" <webmaster@tsukaeru.net> writes:
> 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..
Hmm. Okay, my frontend-out-of-memory theory goes down the drain.
It would seem that the 271'st row in your table is corrupt somehow,
but I'm curious to learn just how. I do not recall any previous
reports of data corruption with exactly this symptom. Would you be
interested in tracing through the backend with a debugger to figure
out what's going wrong? Or giving me or another developer access to
your system to do that?
regards, tom lane
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@tsukaeru.net> To: "Tom Lane" <tgl@sss.pgh.pa.us> Cc: <pgsql-general@postgresql.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@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 > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly >