"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> 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 CON
> 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 st
> "Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> >> Would it be an idea to issue a CLUSTER command after the CREATE TABLE
> >> statement in SQL dumps for tables that have an indisclustered index?
>
> Yeah...
> A CLUSTER command issued just after table creation, while it's
still
> empty,
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
>> Would it be an idea to issue a CLUSTER command after the CREATE TABLE
>> statement in SQL dumps for tables that have an indisclustered index?
Yeah...
> Actually, rather than a full-blown CLUSTER, how about...:
> UPDATE pg_index SET indiscl
> The new cluster is cool in that :
>
> 1. It works
> 2. It saves the indisclustered status
>
> However, after a dump and restore, this indisclustered status will be
lost.
> Would it be an idea to issue a CLUSTER command after the CREATE TABLE
> statement in SQL dumps for tables that have an indisc
