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

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

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
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 16:33:20
Message-ID: 2f4958ff0911250833s22b92dcah9cf3ccac0421b4bc@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Wed, Nov 25, 2009 at 4:26 PM, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov
> wrote:

> Richard Neill <rn214(at)cam(dot)ac(dot)uk> wrote:
>
> > In terms of just index bloat, does a regular vacuum help?
>
> You might want to use the REINDEX command to correct serious index
> bloat.  A regular vacuum will make dead space available for re-use,
> but won't eliminate bloat directly.  (If run regularly, it will
> prevent bloat.)
>
> for that reason, it makes sense to actually partition your data - even tho
you don't see performance degradation because of data size, but purely
because of nature of data.
Other way, is to perform regular cluster && reindex - but this blocks
relations you are clustering..



-- 
GJ

In response to

Responses

pgsql-performance by date

Next:From: Steve CrawfordDate: 2009-11-25 16:45:46
Subject: Re: RAID card recommendation
Previous:From: Kevin GrittnerDate: 2009-11-25 16:26:15
Subject: Re: Query times change by orders of magnitude as DB ages

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