From: Iain <iain@mst.co.jp>
To: wbohl@deepdata.com
To: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: Stopping vacuum
Date: Wed, 30 Jun 2004 10:24:34 +0900
Message-ID: <005b01c45e41$00a16980$7201a8c0@mst1x5r347kymb> (raw)
References: <1088528969.30410.2.camel@sirio>
IIRC killing vacuums can cause some minor problems - i think it may have
been something like index bloat. Tom said something about it once before.
Otherwise, as I understand it, it's "safe" to kill vacuums.
Cheers
Iain
----- Original Message -----
From: "Werner Bohl" <wbohl@deepdata.com>
To: "[ADMIN]" <pgsql-admin@postgresql.org>
Sent: Wednesday, June 30, 2004 2:09 AM
Subject: [ADMIN] Stopping vacuum
> Hi,
>
> We have a very big db that was not vacuumed for a long time. We started
> vacuum 3 days ago and it has not finished yet. There are some urgent
> processes that have to be run against the db.
>
> Is it safe to kill vacuum? It was started with 'vacuum full analyze'
> Is there anyway to speed it up at next start?
>
>
> TIA,
>
> --
> Werner Bohl <wbohl@deepdata.com>
> Infutor de Costa Rica
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: iain@mst.co.jp, wbohl@deepdata.com
Subject: Re: Stopping vacuum
In-Reply-To: <005b01c45e41$00a16980$7201a8c0@mst1x5r347kymb>
References: <1088528969.30410.2.camel@sirio> <005b01c45e41$00a16980$7201a8c0@mst1x5r347kymb>
* 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