From: Matthew T. O'Connor <matthew@zeut.net>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: What is VACUUM waiting for?
Date: Sat, 13 Dec 2008 09:30:36 -0500
Message-ID: <4943C70C.9070307@zeut.net> (raw)
In-Reply-To: <200812122355.25481@zmi.at>
References: <200812122355.25481@zmi.at>
Michael Monnerie wrote:
> Dear list, this is postgres 8.1, and I run a dbmail mailserver where we deleted most e-mails.
> I then did a VACUUM (see below), and just before the "dbmail_messages" truncated rows
> there was a very long time where obviously nothing happened. No CPU usage (<8%) and
> no disk I/O (usage <5%). You can see this from the details:
> DETAIL: CPU 0.11s/0.23u sec elapsed 294.24 sec.
> I would have expected I/Os at least. How does VACUUM work at all?
>
Do you have any vacuum delay setting turned on? Perhaps they are too high?
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-admin@postgresql.org
Cc: matthew@zeut.net, michael.monnerie@is.it-management.at
Subject: Re: What is VACUUM waiting for?
In-Reply-To: <4943C70C.9070307@zeut.net>
* 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