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

Re: BUG #5774: VACCUM & REINDEX kills production environement

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Balamurugan Mahendran <balamurugan(at)adaptavant(dot)com>
Cc: depesz(at)depesz(dot)com, Bala Murugan <b2m(at)a-cti(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5774: VACCUM & REINDEX kills production environement
Date: 2010-11-29 16:52:16
Message-ID: 4CF3DA40.40909@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On 29.11.2010 18:48, Balamurugan Mahendran wrote:
> Thanks, I'll remove it. But I still get down time because of Vacuum(table
> lock). Is there any other better way to do this?

Non-full vacuum doesn't lock out concurrent access. If you're getting 
downtime, there's got to be some other explanation.

> I don't mind to switch to bigger instance with more Hardware.

Based on the information you've provided, it won't make a difference.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-bugs by date

Next:From: Balamurugan MahendranDate: 2010-11-29 17:08:18
Subject: Re: BUG #5774: VACCUM & REINDEX kills production environement
Previous:From: Balamurugan MahendranDate: 2010-11-29 16:48:43
Subject: Re: BUG #5774: VACCUM & REINDEX kills production environement

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