| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Gauri Kanekar" <meetgaurikanekar(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:16:00 |
| Message-ID: | 2e78013d0804290616y78f3825alf8595e5043dc8385@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Apr 29, 2008 at 6:42 PM, Gauri Kanekar
<meetgaurikanekar(at)gmail(dot)com> wrote:
> Thats how our updates works.
> We usually tend to touch the same row many times a day.
>
Then start with a non-100 fillfactor. I would suggest something like
80 and then adjust based on the testing. Since you are anyways have a
update intensive setup, leaving free space in the heap won't harm you
much in the long term.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-04-29 13:48:31 | Re: Replication Syatem |
| Previous Message | Gauri Kanekar | 2008-04-29 13:12:40 | Re: Replication Syatem |