From: | "Gauri Kanekar" <meetgaurikanekar(at)gmail(dot)com> |
---|---|
To: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
Cc: | "Greg Smith" <gsmith(at)gregsmith(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Replication Syatem |
Date: | 2008-04-29 13:12:40 |
Message-ID: | 7e4ba9550804290612v30ef053bj6a7c2fe5600aba27@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Thats how our updates works.
We usually tend to touch the same row many times a day.
~ Gauri
On Tue, Apr 29, 2008 at 6:39 PM, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
wrote:
> On Tue, Apr 29, 2008 at 6:29 PM, Gauri Kanekar
> <meetgaurikanekar(at)gmail(dot)com> wrote:
> >
> >
> > Found that the size increased gradually. Is HOT working over here ??
> > Guide me if im doing something wrong.
> >
>
> You have chosen a bad case for HOT. Since you are repeatedly updating
> the same set of rows, the dead space created in the first step is the
> blocks which are not touched in the subsequent updates. Is this a real
> scenario or are you just testing ? If its just for testing, I would
> suggest updating different sets of rows in each step and then check.
>
> Thanks,
> Pavan
>
>
>
> --
> Pavan Deolasee
> EnterpriseDB http://www.enterprisedb.com
>
--
Regards
Gauri
From | Date | Subject | |
---|---|---|---|
Next Message | Pavan Deolasee | 2008-04-29 13:16:00 | Re: Replication Syatem |
Previous Message | Pavan Deolasee | 2008-04-29 13:09:39 | Re: Replication Syatem |