From: Joe Conway <mail@joeconway.com>
To: Marty Scholes <marty@outputservices.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: rapid degradation after postmaster restart
Date: Sat, 13 Mar 2004 08:07:12 -0800
Message-ID: <405331B0.6080102@joeconway.com> (raw)
In-Reply-To: <4052771A.1080506@outputservices.com>
References: <4052661D.5060505@joeconway.com>
<4052771A.1080506@outputservices.com>
Marty Scholes wrote:
> I have seen similar results to what you are describing.
>
> I found that running a full vacuum:
>
> vacuumdb -fza
>
> followed by a checkpoint makes it run fast again.
>
> Try timing the update with and without a full vacuum.
Will do. I'll let you know how it goes.
Thanks for the reply.
Joe
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: mail@joeconway.com, marty@outputservices.com
Subject: Re: rapid degradation after postmaster restart
In-Reply-To: <405331B0.6080102@joeconway.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