pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Fabio Esposito <nfesposi@sourceweave.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: postgres eating CPU on HP9000
Date: Mon, 29 Mar 2004 12:23:27 -0800
Message-ID: <200403291223.27213.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0403291434220.25470-100000@cr818510-a.basement>
References: <Pine.LNX.4.44.0403291434220.25470-100000@cr818510-a.basement>

Fabio,

> The Vacuum's don't take too long, 10 minutes at most.  I can tell from ps
> -ef | grep and top that its the selects/inserts/updates from the postgres
> related to our app that take all that time up.  If we rerun initdb and
> reload the data, it works great for about two days, then goes bad again.
> 
> We are in the process of trying out 7.4.2 right now, just waiting on the
> reload of pg_dump.

Well, test running VACUUM ANALYZE as the "postgres" superuser and see if that 
fixes the issue.

-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco




view thread (18+ messages)

Message-ID: <200403291223.27213.josh@agliodbs.com>
Permalink:  ../200403291223.27213.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200403291223.27213.josh@agliodbs.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com, nfesposi@sourceweave.net
  Subject: Re: postgres eating CPU on HP9000
  In-Reply-To: <200403291223.27213.josh@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox