Re: Index Bloat Problem - Mailing list pgsql-performance

From Jeff Janes
Subject Re: Index Bloat Problem
Date
Msg-id CAMkU=1z=jOw0BUuxoxYDtcaq+GCdBamN_47TjkZTFkZKJCCnCg@mail.gmail.com
Whole thread Raw
In response to Index Bloat Problem  (Strahinja Kustudić <strahinjak@nordeus.com>)
Responses Re: Index Bloat Problem
List pgsql-performance
On Fri, Aug 10, 2012 at 3:15 PM, Strahinja Kustudić
<strahinjak@nordeus.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


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: 7k records into Sort node, 4.5m out?
Next
From: Doug Hunley
Date:
Subject: cluster on conditional index?