From: Gavin Hamill <gdh@laterooms.com>
To: pgsql-performance@postgresql.org
Subject: Re: VACUUMs take twice as long across all nodes
Date: Thu, 26 Oct 2006 21:35:56 +0100
Message-ID: <20061026213556.174bd7b5.gdh@laterooms.com> (raw)
In-Reply-To: <20061026191728.GD26892@nasby.net>
References: <20061026095827.9e85e1c0.gdh@laterooms.com>
<20196.1161874041@sss.pgh.pa.us>
<20061026160609.5e94e581.gdh@laterooms.com>
<20061026191728.GD26892@nasby.net>
On Thu, 26 Oct 2006 14:17:29 -0500
"Jim C. Nasby" <jim@nasby.net> wrote:
> Are you sure that there's nothing else happening on the machine that
> could affect the vacuum times? Like, say a backup? Or perhaps updates
> coming in from Slony that didn't used to be there?
I'm absolutely certain. The backups run from only one slave, given that
it is a full copy of node 1. Our overnight traffic has not increased
any, and the nightly backups show that the overall size of the DB has
not increased more than usual growth.
Plus, I have fairly verbose logging, and it's not showing anything out
of the ordinary.
Like I said, it's one of those awful hypothesis/hand-waving problems :)
Cheers,
Gavin.
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: gdh@laterooms.com
Subject: Re: VACUUMs take twice as long across all nodes
In-Reply-To: <20061026213556.174bd7b5.gdh@laterooms.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