Skip site navigation (1) Skip section navigation (2)

postmaster proc running CPU to 100% and spinning.

From: Andrew Kelly <akelly(at)transparency(dot)org>
To: pgsql-novice(at)postgresql(dot)org
Subject: postmaster proc running CPU to 100% and spinning.
Date: 2004-03-22 11:48:24
Message-ID: 1079956103.4132.139.camel@hermes.at.home (view raw or flat)
Thread:
Lists: pgsql-novice
Dear all,

my apologies right up front for what is probably going to be a poorly
stated plea. I'm such a novice I'm not even sure how to properly ask the
question.

I'll just dive in...

I've been recently forced to accept the migration of an application that
I don't yet even properly fundamentally understand. The former host and
developer has been a 'hostile' partner in the migration and has not been
forthcoming during any part. I've had to prepare a platform with
incomplete configuration information, and work around what has turned
out to be purposely misleading information. It's been pretty much a
worst case senario from the get-go.
It's hard not to toss off a multi-page rant about this 'organisation',
but I'll just bite my tongue and move on because in spite of it all I've
pretty much got it all whooped.

In a nutshell, the application is a multi-byte encoded database in
postgresql 7.2.4 with a php 4.2.3 front end, hosted on a multiproc
RedHat 7.3 box.

We are about 99% certain we have succeeded in duplicating the platform
and installing the application. So far everything has worked wonderfully
with one single exception.
The application provides the option of performing a new search within
the result set of the previous search. This worked well in the
application on the previous host, but not on the new host. Now, when one
tries to search with the results of a previous search, the postmaster
process drives CPU usage to 100% and the application never returns a
result. Strangely enough, it doesn't max out both processors at the same
time, but the states do change. The maxed out CPU will suddenly drop
under 1% as the second CPU blows out to 100%.
Only kill seems to release the CPU.

Now, I realize there is not enough info here to debug this, but that is
mostly why I'm writing. I know nothing about this app and will have to
plod through the source to learn it. I'm also a cherry to postgresql (to
sql in general).  
My stomache tells me this is config issue with the host in general,
maybe a permissions issue in cache space or something, but I'm only
guessing. The databases were a straightforward dump at the old site and
restore on the new site, and nothing has changed in the source code, and
the fact that everything else runs perfectly seems to indicate it was a
good duplication. 

Can anybody give me a hint on where to start looking and what tools to
use? I'm a flipping nervous wreck suddenly being responsible for
something I don't yet have mastery of.

Andy
-- 


Responses

pgsql-novice by date

Next:From: Stephan SzaboDate: 2004-03-22 14:32:40
Subject: Re: postmaster proc running CPU to 100% and spinning.
Previous:From: Tom LaneDate: 2004-03-21 22:58:44
Subject: Re: Simple list tables question

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group