From: Josh Berkus <josh@agliodbs.com>
To: Bill Chandler <billybobc1210@yahoo.com>
Cc: Mischa Sandberg <mischa.sandberg@telus.net>
Cc: pgsql-perform <pgsql-performance@postgresql.org>
Subject: Re: Index bloat problem?
Date: Thu, 21 Apr 2005 16:56:18 -0700
Message-ID: <200504211656.18324.josh@agliodbs.com> (raw)
In-Reply-To: <20050421225926.11937.qmail@web51404.mail.yahoo.com>
References: <20050421225926.11937.qmail@web51404.mail.yahoo.com>
Bill,
> If I deleted 75% of the rows but had a max_fsm_pages
> setting that still exceeded the pages required (as
> indicated in VACUUM output), would that solve my
> indexing problem or would I still need to REINDEX
> after such a purge?
Depends on the performance you're expecting. The FSM relates the the re-use
of nodes, not taking up free space. So after you've deleted 75% of rows,
the index wouldn't shrink. It just wouldn't grow when you start adding rows.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, billybobc1210@yahoo.com, mischa.sandberg@telus.net
Subject: Re: Index bloat problem?
In-Reply-To: <200504211656.18324.josh@agliodbs.com>
* 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