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 17:08:18 |
Message-ID: | AANLkTikDY1c+QQg-1XTHH4YvsVVPFbBK9Rzs07sX_qCJ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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:22 PM, Heikki Linnakangas <
heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-29 18:27:38 | Re: BUG #5761: In 'dblink' function connection string truncated |
Previous Message | Heikki Linnakangas | 2010-11-29 16:52:16 | Re: BUG #5774: VACCUM & REINDEX kills production environement |