Re: Query times change by orders of magnitude as DB ages

Matthew Wakeling wrote:
> On Wed, 25 Nov 2009, Richard Neill wrote:
>>> On Sun, 22 Nov 2009, Richard Neill wrote:
>>>> Worse still, doing a cluster of most of the tables and vacuum full
>>>> analyze
>
> In fact, cluster is exactly the command you are looking for. It will
> drop the indexes, do a complete table rewrite (in the correct order),
> and then recreate all the indexes again.
>
> In normal operation, a regular vacuum will keep the table under control,
> but if you actually want to shrink the database files in exceptional
> circumstances, then cluster is the tool for the job.
>

Thanks - now I understand.

In terms of just index bloat, does a regular vacuum help?

Richard