| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)postgresql(dot)org> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER INDEX set fillfactor |
| Date: | 2007-10-06 07:33:30 |
| Message-ID: | 1191656010.4223.461.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Fri, 2007-10-05 at 21:24 +0100, Dave Page wrote:
> Simon Riggs wrote:
> > It would be even better if there was an option to do that CONCURRENTLY,
> > i.e. add the new index and then drop the old one afterwards. (It's
> > unfortunate that there isn't a REINDEX concurrently, but there isn't
> > yet).
>
> Funny - I suggested that to Greg just the other day...
Sorry, I meant in the absence of REINDEX concurrently, we can issue:
CREATE INDEX CONCURRENTLY newindex
DROP INDEX oldindex
on each index on the table in turn, which does the same thing.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2007-10-06 16:45:52 | Re: ALTER INDEX set fillfactor |
| Previous Message | Dave Page | 2007-10-05 20:24:40 | Re: ALTER INDEX set fillfactor |