> No; directly manipulating the system catalogs in dump scripts is a > crummy idea, because (a) it only works if you're superuser, and (b) > it creates a nasty backwards-compatibility problem if we change the > catalogs involved. > > A CLUSTER command issued just after table creation, while it's still > empty, would be cheap ... but we don't put the index in place until > we've loaded the data, do we? Darn.
Maybe we should issue it after the CREATE INDEX and ADD CONSTRAINT has occurred and just bite it. We could have a pg_dump --no-cluster option to suppress them. However, we need to guarantee to the user that we restore their database exactly as they had it. Other potential problem - ALTER TABLE / SET STORAGE ? Chris ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
