From: Graham Davis <gdavis@refractions.net>
To: pgsql-performance@postgresql.org
Subject: index growth problem
Date: Wed, 18 Oct 2006 15:20:19 -0700
Message-ID: <4536A8A3.1050409@refractions.net> (raw)
In-Reply-To: <eg1dai$1tfa$1@news.hub.org>
References: <eft782$5a1$1@news.hub.org>
<b42b73150610030804q2719222du57c63a085e26a5a4@mail.gmail.com>
<efu8tf$1blk$1@news.hub.org>
<b42b73150610031221y4955e663ped999a83a810d318@mail.gmail.com>
<eg0u6e$hbr$1@news.hub.org>
<b42b73150610041407y3554f311u1329c4f3bdc53999@mail.gmail.com>
<eg1dai$1tfa$1@news.hub.org>
I have a question about index growth.
The way I understand it, dead tuples in indexes were not reclaimed by
VACUUM commands in the past. However, I've read in a few forum posts
that this was changed somewhere between 7.4 and 8.0.
I'm having an issue where my GIST indexes are growing quite large, and
running a VACUUM doesn't appear to remove the dead tuples. For example,
if I check out the size an index before running any VACUUM :
select pg_relation_size('asset_positions_position_idx');
pg_relation_size
------------------
11624448
(1 row)
The size is about 11Mb. If I run a VACUUM command in verbose, I see
this about the index:
INFO: index "asset_positions_position_idx" now contains 4373 row
versions in 68 pages
DETAIL: 0 index pages have been deleted, 0 are currently reusable.
CPU 0.00s/0.00u sec elapsed 0.16 sec.
When I run the same command to find the size after the VACUUM, it hasn't
changed. However, if I drop and then recreate this index, the size
becomes much smaller (almost half the size):
drop index asset_positions_position_idx;
DROP INDEX
CREATE INDEX asset_positions_position_idx ON asset_positions USING GIST
(position GIST_GEOMETRY_OPS);
CREATE INDEX
select pg_relation_size('asset_positions_position_idx');
pg_relation_size
------------------
6225920
(1 row)
Is there something I am missing here, or is the reclaiming of dead
tuples for these indexes just not working when I run a VACUUM? Is it
suppose to work?
--
Graham Davis
Refractions Research Inc.
gdavis@refractions.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gdavis@refractions.net
Subject: Re: index growth problem
In-Reply-To: <4536A8A3.1050409@refractions.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox