Re: BUG #5774: VACCUM & REINDEX kills production environement - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #5774: VACCUM & REINDEX kills production environement
Date
Msg-id 4CF3DA40.40909@enterprisedb.com
Whole thread Raw
In response to BUG #5774: VACCUM & REINDEX kills production environement  ("Bala Murugan" <b2m@a-cti.com>)
Responses Re: BUG #5774: VACCUM & REINDEX kills production environement  (Balamurugan Mahendran <balamurugan@adaptavant.com>)
List 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

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #5774: VACCUM & REINDEX kills production environement
Next
From: queej
Date:
Subject: Re: BUG #5761: In 'dblink' function connection string truncated