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

Re: Stopping vacuum

From: "CHRIS HOOVER" <CHRIS(dot)HOOVER(at)companiongroup(dot)com>
To: wbohl(at)deepdata(dot)com, pgsql-admin(at)postgresql(dot)org
Subject: Re: Stopping vacuum
Date: 2004-06-29 17:30:00
Message-ID: NX236d63-62f13f0a@companiongroup.com (view raw or flat)
Thread:
Lists: pgsql-admin
It is safe to kill the vacuum (but not a favored thing to do).  I have done it
many times when the vacuums have run to long and have started to affect my
online production performance.  Be sure to just do a kill, as a kill -9 will
cause the db to reset all connections to it.

Since you have not vacuumed this db in so long, I would probably suggest
vacuuming it table by table so you can have a finer level of control over the
vacuum.

HTH,

Chris
------------------( Forwarded letter 1 follows )---------------------
Date: Tue, 29 Jun 2004 11:09:29 -0600
To: (dot)ADMIN(dot)[pgsql-admin](at)postgresql(dot)org(dot)comp
From: Werner(dot)Bohl[wbohl](at)deepdata(dot)com(dot)comp
Sender: pgsql-admin-owner+m14031(at)postgresql(dot)org(dot)comp
Reply-To: wbohl(at)deepdata(dot)com(dot)comp
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

pgsql-admin by date

Next:From: Josh BerkusDate: 2004-06-29 17:36:48
Subject: Re: lock timeout patch
Previous:From: Werner BohlDate: 2004-06-29 17:09:29
Subject: Stopping vacuum

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