Re: [BUGS] BUG #5774: VACCUM & REINDEX kills production environement

2010-11-29 Thread Alvaro Herrera
Excerpts from Balamurugan Mahendran's message of lun nov 29 13:48:43 -0300 2010: > 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? I don't mind to switch to > bigger instance with more Hardware. I wonder if you're doing s

Re: [BUGS] BUG #5774: VACCUM & REINDEX kills production environement

2010-11-29 Thread Balamurugan Mahendran
Is there a recommended link/documentation to make sure my configuration? for my current hardware 7 GB of memory 20 EC2 Compute Units (8 virtual cores with 2.5 EC2 Compute Units each) 1690 GB of instance storage 64-bit platform Thanks for all your help!! Thanks, Bala On Mon, Nov 29, 2010 at 10:

Re: [BUGS] BUG #5774: VACCUM & REINDEX kills production environement

2010-11-29 Thread Balamurugan Mahendran
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? I don't mind to switch to bigger instance with more Hardware. Current Instance : 7 GB of memory 20 EC2 Compute Units (8 virtual cores with 2.5 EC2 Compute Units each) 1690 GB

Re: [BUGS] BUG #5774: VACCUM & REINDEX kills production environement

2010-11-29 Thread Heikki Linnakangas
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.

Re: [BUGS] BUG #5774: VACCUM & REINDEX kills production environement

2010-11-29 Thread Heikki Linnakangas
On 29.11.2010 17:16, Balamurugan Mahendran wrote: This is how I used to do maintenance through cron job. Please advise if i need to change my method, Also I used to run re-index all the time while doing Vacuum (cron job updated twice a week). Most likely you can just remove the reindex commands

Re: [BUGS] BUG #5774: VACCUM & REINDEX kills production environement

2010-11-29 Thread Balamurugan Mahendran
This is how I used to do maintenance through cron job. Please advise if i need to change my method, Also I used to run re-index all the time while doing Vacuum (cron job updated twice a week). queryfor Vaccum:VACUUM VERBOSE ANALYZE contactmanagementsystem.brands queryfor Vaccum:VACUUM VERBOSE ANAL

Re: [BUGS] BUG #5774: VACCUM & REINDEX kills production environement

2010-11-28 Thread hubert depesz lubaczewski
On Sun, Nov 28, 2010 at 07:25:52AM +, Bala Murugan wrote: > > The following bug has been logged online: > > Bug reference: 5774 > Logged by: Bala Murugan > Email address: b...@a-cti.com > PostgreSQL version: 8.3.7 > Operating system: openSUSE 10.3 (X86-64) - Kernel \r (\l

[BUGS] BUG #5774: VACCUM & REINDEX kills production environement

2010-11-28 Thread Bala Murugan
The following bug has been logged online: Bug reference: 5774 Logged by: Bala Murugan Email address: b...@a-cti.com PostgreSQL version: 8.3.7 Operating system: openSUSE 10.3 (X86-64) - Kernel \r (\l). Description:VACCUM & REINDEX kills production environement Details: