Skip site navigation (1) Skip section navigation (2)

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

From: Richard Neill <rn214(at)cam(dot)ac(dot)uk>
To:
Cc: Richard Neill <rn214(at)cam(dot)ac(dot)uk>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Query times change by orders of magnitude as DB ages
Date: 2009-11-25 12:22:40
Message-ID: 4B0D2190.8060200@cam.ac.uk (view raw or flat)
Thread:
Lists: pgsql-performance

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

In response to

Responses

pgsql-performance by date

Next:From: Richard NeillDate: 2009-11-25 12:27:28
Subject: Re: Query times change by orders of magnitude as DB ages
Previous:From: Matthew WakelingDate: 2009-11-25 12:18:53
Subject: Re: Query times change by orders of magnitude as DB ages

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group