From: Tom Lane <tgl@sss.pgh.pa.us>
To: silviapg@tiscali.it <silviapg@tiscali.it>
Cc: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: postgres eating CPU
Date: Wed, 17 Nov 2004 18:38:40 -0500
Message-ID: <5433.1100734720@sss.pgh.pa.us> (raw)
In-Reply-To: <419BD5DF.5090902@tiscali.it>
References: <419BCD20.4010906@tiscali.it>
<200411171427.13134.josh@agliodbs.com>
<419BD5DF.5090902@tiscali.it>
"silviapg@tiscali.it" <silviapg@tiscali.it> writes:
> in March there was an interesting discussion on the list with the
> subject "postgres eating CPU on HP9000".
> http://archives.postgresql.org/pgsql-performance/2004-03/msg00380.php
Reviewing that, the problem is most likely that (a) they didn't have
max_fsm_pages set high enough to cover the database, and (b) they were
running 7.3.* which is prone to index bloat.
regards, tom lane
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: tgl@sss.pgh.pa.us, silviapg@tiscali.it, josh@agliodbs.com
Subject: Re: postgres eating CPU
In-Reply-To: <5433.1100734720@sss.pgh.pa.us>
* 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