From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-admin@postgresql.org, "Gregory Maxwell" <gmaxwell@gmail.com>
Subject: Re: Bloated pg_shdepend_depender_index
Date: Fri, 24 Mar 2006 10:02:01 -0500
Message-ID: <4553.1143212521@sss.pgh.pa.us> (raw)
In-Reply-To: <200603241150.20021.peter_e@gmx.net>
References: <e692861c0603231716j63d712eemfe7292ff968801a9@mail.gmail.com>
<e692861c0603231958m11472300gb1c32cf0e998a3cd@mail.gmail.com>
<27588.1143175698@sss.pgh.pa.us>
<200603241150.20021.peter_e@gmx.net>
Peter Eisentraut <peter_e@gmx.net> writes:
> Am Freitag, 24. März 2006 05:48 schrieb Tom Lane:
>> Well, the VACUUM FULL algorithm is incapable of shrinking indexes ---
>> the only way is REINDEX, or something else that reconstructs indexes
>> from scratch, such as CLUSTER. One of the things we need to look into
>> is putting more smarts into VACUUM so that it automatically does
>> something reasonable when faced with extreme cases like these.
> If the user is running VACUUM FULL, he has presumably determined that the
> table is too bloated to be recovered in a graceful way, and quite likely the
> indexes are going to be bloated similarly. So seemingly one might as well
> launch a reindexing on the table after VACUUM FULL has done its thing.
> Whether that should be automatic is another question but perhaps the advice
> should be documented somewhere?
Actually, I wonder whether VACUUM FULL shouldn't be thrown away and
replaced by something else entirely. That algorithm only really works
nicely when just a small percentage of the rows need to be moved to
re-compact the table --- if you're moving lots of rows, it makes the
index bloat situation *worse* not better because of the transient need
for index entries pointing to both copies of moved rows. Lazy VACUUM
has become the de-facto standard for situations where there's not a huge
amount of empty space, and so it's not clear where the sweet spot is for
VACUUM FULL anymore. If you've got enough disk space, a rewrite (like
CLUSTER or ALTER TABLE) is going to blow the doors off VACUUM FULL,
let alone VACUUM FULL plus REINDEX. Not to mention that for
sufficiently huge tables, VACUUM FULL fails outright because it runs out
of RAM.
We need to fix CLUSTER to make it MVCC-safe (ie, not discard
recently-dead rows), and it'd be nice to have something like it that
didn't worry about ordering but just did a seqscan of the source table.
Then I'd be inclined to recommend that instead of VACUUM FULL for most
cases of severe bloat.
Unfortunately this all breaks down for shared system catalogs and the
core (nailed-in) catalogs, because we can't change their relfilenodes
and so the crash-safe CLUSTER/REINDEX approach doesn't work. We still
need a new idea or two there.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter_e@gmx.net, gmaxwell@gmail.com
Subject: Re: Bloated pg_shdepend_depender_index
In-Reply-To: <4553.1143212521@sss.pgh.pa.us>
References: <e692861c0603231716j63d712eemfe7292ff968801a9@mail.gmail.com> <e692861c0603231958m11472300gb1c32cf0e998a3cd@mail.gmail.com> <27588.1143175698@sss.pgh.pa.us> <200603241150.20021.peter_e@gmx.net> <4553.1143212521@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