From: Tom Lane <tgl@sss.pgh.pa.us>
To: Seum-Lim Gan <slgan@lucent.com>
Cc: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org
Subject: Re: index file bloating still in 7.4 ?
Date: Mon, 20 Oct 2003 17:42:52 -0400
Message-ID: <15968.1066686172@sss.pgh.pa.us> (raw)
In-Reply-To: <p05100318bbb86e62801a@[192.168.10.52]>
References: <p0510030cbbb7667a7f87@[192.168.10.52]>
<200310181458.15575.josh@agliodbs.com>
<p0510030dbbb79c742da5@[192.168.10.52]>
<16213.1066530060@sss.pgh.pa.us>
<p0510030ebbb7cabb0ceb@[192.168.10.52]>
<17172.1066542509@sss.pgh.pa.us>
<p05100313bbb852b0fe68@[192.168.10.52]>
<19692.1066578442@sss.pgh.pa.us>
<p05100318bbb86e62801a@[192.168.10.52]>
Seum-Lim Gan <slgan@lucent.com> writes:
> [ successive outputs from VACUUM ANALYZE ]
FWIW, I don't think your problem is really index bloat at all, it's
more like too-many-dead-rows bloat. Note that the number of "dead row
versions" is climbing steadily from run to run:
> DETAIL: 101802 dead row versions cannot be removed yet.
> DETAIL: 110900 dead row versions cannot be removed yet.
> DETAIL: 753064 dead row versions cannot be removed yet.
> DETAIL: 765328 dead row versions cannot be removed yet.
It's hardly the index's fault that it's growing, when it has to keep
track of an ever-increasing number of rows.
The real question is what you're doing that requires the system to keep
hold of these dead rows instead of recycling them. I suspect you have
a client process somewhere that is holding an open transaction for a
long time ... probably not doing anything, just sitting there with an
unclosed BEGIN ...
regards, tom lane
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: tgl@sss.pgh.pa.us, slgan@lucent.com, josh@agliodbs.com
Subject: Re: index file bloating still in 7.4 ?
In-Reply-To: <15968.1066686172@sss.pgh.pa.us>
* 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