Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
ALTER INDEX set fillfactor
- From: Simon Riggs <simon(at)2ndquadrant(dot)com>
- To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
- Subject: ALTER INDEX set fillfactor
- Date: Thu, 04 Oct 2007 15:23:50 +0100
- Message-id: <1191507830(dot)4223(dot)133(dot)camel(at)ebony(dot)site>
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. 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. 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). -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com
- Follow-Ups:
- Re: ALTER INDEX set fillfactor
- From: Dave Page
- Re: ALTER INDEX set fillfactor
- Prev by Date: CREATE INDEX CONCURRENTLY
- Next by Date: SVN Commit by hiroshi: r6711 - in trunk/pgadmin3: . pgadmin/dlg
- Previous by thread: CREATE INDEX CONCURRENTLY
- Next by thread: Re: ALTER INDEX set fillfactor
- Indexes: