| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | S H <msq001(at)live(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: bloating vacuum |
| Date: | 2013-05-14 15:31:08 |
| Message-ID: | CAOR=d=0Umu--fTgv-4BqYQpRBjNj_dWDKZqshqfCKEX8CxFcvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, May 14, 2013 at 9:06 AM, S H <msq001(at)live(dot)com> wrote:
> Got some information from following
>
> http://www.depesz.com/2011/07/06/bloat-happens/
>
> What is the general solution to avoid bloating.
1: Don't do massive deletes
2: Make sure your autovacuum is tuned aggressively enough to keep up
with your workload
3: Make sure your hardware is fast enough to allow autovacuum to be
tuned aggressively enough to keep up with your workload.
Some minor bloating is fine. 10, 20, 50% dead space in a table is no
big deal. OTOH, 99.99% dead space probably is.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Neyman | 2013-05-14 15:48:07 | Re: Running out of memory on vacuum |
| Previous Message | Ioana Danes | 2013-05-14 15:29:29 | Re: Running out of memory on vacuum |