From: Robert Creager <Robert_Creager@StorageTek.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Huge performance problem between 7.4.1 and 8.0.3 - CS issue?
Date: Tue, 19 Jul 2005 10:50:14 -0600
Message-ID: <20050719105014.00007635@C118181.stortek.com> (raw)
In-Reply-To: <15472.1121709173@sss.pgh.pa.us>
References: <20050718114952.00004ac5@C118181.stortek.com>
<15472.1121709173@sss.pgh.pa.us>
On Mon, 18 Jul 2005 13:52:53 -0400
Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Start a fresh psql session and "SHOW vacuum_cost_delay" to verify what
> the active setting is.
>
Alright. Restarted the 803 database. Cron based vacuum analyze is running
every 5 minutes. vacuum_cost_delay is 0. The problem showed up after about 1/2
hour of running. I've got vacuum jobs stacked from the last 35 minutes, with 2
vacuums running at the same time. CS is around 73k.
What do I do now? I can bring the db back to normal and not run any cron based
vacuum to see if it still happens, but I suspect nothing will happen without the
vacuum. I'll leave it in it's current semi-catatonic state as long as possible
in case there is something to look at?
Cheers,
Rob
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: Robert_Creager@StorageTek.com, tgl@sss.pgh.pa.us
Subject: Re: Huge performance problem between 7.4.1 and 8.0.3 - CS issue?
In-Reply-To: <20050719105014.00007635@C118181.stortek.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