Re: OT: postgres 8.1 features ... possible pressure on migration of features from enterprise edition down to standard edition?

On 08/11/05, Paul Drake <bdbafh_at_gmail.com> wrote:
> "Make REINDEX DATABASE reindex all indexes in the database ".
>

I can see where something like that might be useful (although probably more useful at the schema level) *if* it were coupled with a 'disable indexes' command. Currently it is quite common, when doing a batch load, to first drop all indexes then do the load and recreate the indexes afterwards. This does rely on you knowing all the indexes in your database and updating the scripts that do the drop and recreate to take account of any changes (new indexes, dropped indexes, columns added to or removed from an index, indexes moved to a different tablespace &c). It might be easier if there was someway to just disable all the indexes (they're still there, they just won't be updated or used in queries) before the load then re-enable and rebuild them with just a couple of commands.

I know that as a DBA you should know what's going on with the database interms of new indexes &c, but that does presuppose that you have absolute authority and only you know the passwords. In reality the application support team will almost certainly have the schema owner password and it would only take for one of them to decide that going through change control is too labourious for 'just a couple of indexes' to possibly cause problems.

Stephen

--
It's better to ask a silly question than to make a silly assumption.

http://stephensorablog.blogspot.com/
--
http://www.freelists.org/webpage/oracle-l