Re: Index Bloat Problem

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Strahinja Kustudić <strahinjak(at)nordeus(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Index Bloat Problem
Date: 2012-08-14 04:14:42
Message-ID: CAMkU=1z=jOw0BUuxoxYDtcaq+GCdBamN_47TjkZTFkZKJCCnCg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Aug 10, 2012 at 3:15 PM, Strahinja Kustudić
<strahinjak(at)nordeus(dot)com> wrote:
>
> For example, yesterday when I checked the database size on the production
> server it was 30GB, and the restored dump of that database was only 17GB.
> The most interesting thing is that the data wasn't bloated that much, but
> the indices were. Some of them were a few times bigger than they should be.
> For example an index on the production db is 440MB, while that same index
> after dump/restore is 17MB, and there are many indices with that high
> difference.

Could your pattern of deletions be leaving sparsely populated, but not
completely empty, index pages; which your insertions will then never
reuse because they never again insert values in that key range?

Cheers,

Jeff

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Doug Hunley 2012-08-14 15:27:18 cluster on conditional index?
Previous Message Tom Lane 2012-08-14 02:11:45 Re: 7k records into Sort node, 4.5m out?