Skip site navigation (1) Skip section navigation (2)

Re: Stopping vacuum

From: "Iain" <iain(at)mst(dot)co(dot)jp>
To: <wbohl(at)deepdata(dot)com>, "[ADMIN]" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Stopping vacuum
Date: 2004-06-30 01:24:34
Message-ID: 005b01c45e41$00a16980$7201a8c0@mst1x5r347kymb (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
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.


----- Original Message ----- 
From: "Werner Bohl" <wbohl(at)deepdata(dot)com>
To: "[ADMIN]" <pgsql-admin(at)postgresql(dot)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(at)deepdata(dot)com>
> Infutor de Costa Rica
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org

In response to

pgsql-admin by date

Next:From: 周仁军Date: 2004-06-30 02:05:15
Subject: unsubscribe
Previous:From: Joe ConwayDate: 2004-06-29 22:27:59
Subject: Re: grant execute on many functions

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group