From: | "David Esposito" <pgsql-general(at)esposito(dot)newnetco(dot)com> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: index bloat |
Date: | 2005-07-18 11:47:52 |
Message-ID: | 200507181147.j6IBlquj010724@relay1.nnco.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
This week is looking busy for me but hopefully I'll be able to play around
with various vacuuming frequencies for this table ...
Thanks for all of your help; I'll report on my progress
-Dave
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Wednesday, July 13, 2005 5:40 PM
>
> 1. VACUUM more often than once per day.
>
> 2. Live with a steady-state index size that's about 5x the minimum.
>
> I'd recommend taking a hard look at choice #1 --- you could experiment
> with using the "vacuum cost delay" settings to tamp down VACUUM's I/O
> demand to the point where it doesn't kill interactive performance, and
> then run it maybe every hour or two on the table(s) where you
> have this
> problem.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2005-07-18 11:56:00 | Re: (Win32 Postgres) Slow to Connect first - OK afterwards |
Previous Message | Andrus | 2005-07-18 11:39:06 | Re: How to create unique constraint on NULL columns |