From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER INDEX set fillfactor |
Date: | 2007-10-05 20:24:40 |
Message-ID: | 47069D88.3020100@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Simon Riggs wrote:
> pgadmin sneaks a REINDEX into the SQL when you specify a change to the
> fillfactor of an index.
>
> That's not very handy because the Postgres manual says specifically that
> ALTER INDEX doesn't issue a REINDEX. It's a perfectly valid thing to run
> on its own, since it will affect the future growth of the index.
Thanks, fixed in SVN.
> Issuing the REINDEX can lock the table for hours and shouldn't be issued
> quietly on production systems. There should be a REINDEX immediate
> option, or a reminder prompt.
Yeah - not this close to a release though.
> 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...
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-10-06 07:33:30 | Re: ALTER INDEX set fillfactor |
Previous Message | svn | 2007-10-05 20:22:31 | SVN Commit by dpage: r6716 - trunk/pgadmin3/pgadmin/dlg |