Hello,
if vacuuming does not help, you may also want to log all queries
running more than x milliseconds to help localize the
problem.
see log_min_duration_statement=xxxx #ms in
postgresql.conf
(i didn't check its avaibility in older
version)
HTH,
Marc
From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of MC Moisei
Sent: Friday, June 08, 2007 11:11 PM
To: pgsql-general@xxxxxxxxxxxxxx
Subject: Re: [GENERAL] Postmaster processes taking all the CPU
I did that remotely, thru the psqladmin. How do I
do it from that box ?
> Date: Fri, 8 Jun 2007 16:41:57 -0400
> From: esconsult1@xxxxxxxxx
> Subject: Re: [GENERAL] Postmaster processes taking all the CPU
> CC: pgsql-general@xxxxxxxxxxxxxx
>
> Have you done a full vacuum and not just a reqular vacuum?
>
> - Ericson Smith
> Developer
> http://www.funadvice.com
>
> On 6/8/07, Andrew Sullivan <ajs@xxxxxxxxxxxxxxx> wrote:
> > On Fri, Jun 08, 2007 at 03:20:28PM -0500, MC Moisei wrote:
> > >
> > > pack of postmaster(4-22) processes ran by postgres user are taking
> > > over almost all the CPU.
> >
> > What else is the box doing? If it doesn't have any other work to do,
> > why shouldn't postgres use the CPU time? (This is a way of saying,
> > "You didn't tell us anything that would allow us to help.")
> >
> > A
> >
> > --
> > Andrew Sullivan | ajs@xxxxxxxxxxxxxxx
> > In the future this spectacle of the middle classes shocking the avant-
> > garde will probably become the textbook definition of Postmodernism.
> > --Brad Holland
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 4: Have you searched our list archives?
> >
> > http://archives.postgresql.org/
> >
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
