Re: Runaway backend at 100% CPU PostgreSQL v8.3.5 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Runaway backend at 100% CPU PostgreSQL v8.3.5
Date
Msg-id 13175.1231284117@sss.pgh.pa.us
Whole thread Raw
In response to Runaway backend at 100% CPU PostgreSQL v8.3.5  ("Stephen R. van den Berg" <srb@cuci.nl>)
Responses Re: Runaway backend at 100% CPU PostgreSQL v8.3.5  ("Stephen R. van den Berg" <srb@cuci.nl>)
List pgsql-hackers
"Stephen R. van den Berg" <srb@cuci.nl> writes:
> It seems that the backend is stuck in some kind of endless loop.  Since
> it's a production Debian server, the backend is not compiled with debugging
> turned on.  The best I can do is ltrace it, in hopes of someone recognising
> the infinite sequence.

Well, it seems to be repeatedly executing a SPI call, which suggests but
doesn't prove that it's in a PL function ... but how would it get into
one while in PARSE state?

Anyway there's not much data here.  You might try attaching to the
backend process with gdb and trying "bt" and "p debug_query_string";
I think you should get something out of that even without debug symbols.
If not, maybe turning on query logging would be worthwhile.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Re: [COMMITTERS] pgsql: This makes all the \dX commands (most importantly to most: \df)
Next
From: Bruce Momjian
Date:
Subject: Re: Re: [COMMITTERS] pgsql: This makes all the \dX commands (most importantly to most: \df)