| From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| 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 09:11:17 |
| Message-ID: | 1169197877.11526.10.camel@coppola.muc.ecircle.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
[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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-01-19 09:47:13 | Re: [HACKERS] Autovacuum Improvements |
| Previous Message | Magnus Hagander | 2007-01-19 08:38:00 | Re: Defining data directory while installing [WinXP] |