From: Csaba Nagy <nagy@ecircle-ag.com>
To: Ed L. <pgsql@bluepolka.net>
Cc: Postgres general mailing list <pgsql-general@postgresql.org>
Cc: Bill Moran <wmoran@collaborativefusion.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Subject: Re: Index bloat of 4x
Date: Fri, 19 Jan 2007 10:11:17 +0100
Message-ID: <1169197877.11526.10.camel@coppola.muc.ecircle.de> (raw)
In-Reply-To: <200701181842.00696.pgsql@bluepolka.net>
References: <20070117093223.bcdb302e.wmoran@collaborativefusion.com>
<19674.1169104105@sss.pgh.pa.us>
<20070118080715.479b9315.wmoran@collaborativefusion.com>
<200701181842.00696.pgsql@bluepolka.net>
[snip]
> I afraid I don't see how any of the answers I saw discussed fit a
> 24x7 operation. Reindex, drop index, vacuum full, ... they all
> block production queries of one sort or another for significant
> periods of time (minutes) on large (multi/tens of GB) tables,
> and thus are infeasible for true 24x7 operations.[snip]
This is not completely true, as of 8.2 there is an online index build,
and if that could be used in a background thread to rebuild the index
and replace the bloated one once it's finished, that would be a
non-blocking operation which could be done in 24x7 situations.
There are some issues with using the online index build for replacing an
existing index, but if those could be solved it would be a viable
solution I think...
Cheers,
Csaba.
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-general@postgresql.org
Cc: nagy@ecircle-ag.com, pgsql@bluepolka.net, wmoran@collaborativefusion.com, tgl@sss.pgh.pa.us, alvherre@commandprompt.com
Subject: Re: Index bloat of 4x
In-Reply-To: <1169197877.11526.10.camel@coppola.muc.ecircle.de>
* 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