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: 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:11:09
Message-ID: 4B0D1EDD.3070909@cam.ac.uk (view raw or flat)
Thread:
Lists: pgsql-performance

Matthew Wakeling wrote:
> On Sun, 22 Nov 2009, Richard Neill wrote:
>> Worse still, doing a cluster of most of the tables and vacuum full 
>> analyze
> 
> Why are you doing a vacuum full? That command is not meant to be used 
> except in the most unusual of circumstances, as it causes bloat to indexes.

We'd left it too long, and the DB was reaching 90% of disk space. I
didn't realise that vacuum full was ever actively bad, only sometimes
unneeded. I do now - thanks for the tip.

> 
> If you have run a cluster command, then running vacuum full will make 
> the table and index layout worse, not better.
> 

So, having managed to bloat the indexes in this way, what can I do to
fix it? Will a regular vacuum do the job?

Richard


In response to

Responses

pgsql-performance by date

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

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