> 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 ?
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2003-02-24 02:33:33|
|Subject: Re: Loss of cluster status |
|Previous:||From: Peter Eisentraut||Date: 2003-02-23 23:36:04|
|Subject: Re: pg_dump / restore of empty database gives errors |