| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
| Cc: | Postgres general mailing list <pgsql-general(at)postgresql(dot)org>, Bill Moran <wmoran(at)collaborativefusion(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: Index bloat of 4x |
| Date: | 2007-01-19 17:19:52 |
| Message-ID: | 200701191019.52768.pgsql@bluepolka.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday January 19 2007 2:11 am, Csaba Nagy wrote:
>
> > 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.
Online index creation definitely helps us toward 24x7. But
wouldn't we still have to drop the old index, thus blocking
production queries?
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-01-19 17:45:03 | Re: Index bloat of 4x |
| Previous Message | Tom Lane | 2007-01-19 17:12:36 | Re: Clearing plans |