| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | "Gauri Kanekar" <meetgaurikanekar(at)gmail(dot)com>, "Shane Ambler" <pgsql(at)sheeky(dot)biz>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Replication Syatem |
| Date: | 2008-04-30 13:35:29 |
| Message-ID: | 481875A1.4060502@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Craig Ringer wrote:
> Heikki Linnakangas wrote:
>
>> Did you dump and reload the table after setting the fill factor? It
>> only affects newly inserted data.
>
> VACUUM FULL or CLUSTER should do the job too, right? After all, they
> recreate the table so they must take the fillfactor into account.
CLUSTER, yes. VACUUM FULL won't move tuples around just to make room for
the fillfactor.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2008-04-30 13:36:12 | Re: Replication Syatem |
| Previous Message | Craig Ringer | 2008-04-30 12:16:21 | Re: Replication Syatem |