From: | Balamurugan Mahendran <balamurugan(at)adaptavant(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(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:48:43 |
Message-ID: | AANLkTimxpS7Zw1CH+HH7Dvtx40gEfOENrLoZq5nO97bL@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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 of instance storage
64-bit platform
I/O Performance: High
I can go for this : (Only if this helps me from Outage)
34.2 GB of memory
13 EC2 Compute Units (4 virtual cores with 3.25 EC2 Compute Units each)
850 GB of instance storage
64-bit platform
I/O Performance: High
Thanks,
Bala
On Mon, Nov 29, 2010 at 10:01 PM, Heikki Linnakangas <
heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> 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. Routing reindexing is
> not normally needed.
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-11-29 16:52:16 | Re: BUG #5774: VACCUM & REINDEX kills production environement |
Previous Message | Heikki Linnakangas | 2010-11-29 16:31:55 | Re: BUG #5774: VACCUM & REINDEX kills production environement |