| From: | Venkata Balaji Nagothi <vbnpgc(at)gmail(dot)com> |
|---|---|
| To: | Elanchezhiyan Elango <elanelango(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Vacuuming strategy |
| Date: | 2014-05-02 00:35:18 |
| Message-ID: | CAHBAh5tTnZqbUc7kXcsKW+5FcvUfJ-txMOG_piUJ3hCojQR-3A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 30, 2014 at 9:59 AM, Elanchezhiyan Elango
<elanelango(at)gmail(dot)com>wrote:
> Hi,
>
> I need help on deciding my vacuuming strategy. I need to know if I ever
> need to do 'vacuum full' for my tables.
>
>
Important and critical configuration is "fillfactor". "fillfactor" will
have a greater impact on VACUUMING strategy. It will further help reduce or
even remove the dependency on VACUUM FULL.
If possible, please set the fillfactor to an optimal value for Tables and
Indexes which are undergoing high DMLs. May be you should start with a
value between 50 to 70.
Only problem is - You will need to do a one-time VACUUM FULL immediately
after you change the fillfactor.
Regards,
Venkata Balaji N
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prashanth Kumar | 2014-05-02 00:38:44 | Revoke Connect |
| Previous Message | Seb | 2014-05-01 21:53:35 | Re: break table into portions for writing to separate files |