Thread: Re: CLUSTER. (fwd)

> It's done with CLUSTER indeed. Everything is copied in a temp table which is later renamed to the original table, so
allgrant perimissions and indeces are lost on this table. Also keep in mind that you'll get new OIDs too (if you are
dependingon them) 
Is very any way of going cluster without losing anything?
At this point I am able to dump/restore database, but soon it'll become
rather impossible for some time.
Do I have to 'cluster' before putting any data in dbase?

Clustering is really static i.e. it's done and after it any inserts/updates start spoiling the table again. So I guess
theanswer is no. Maybe you can create a procedure that does CLUSTER and then recreates the indeces and whatever else
youlose in the process. 

cheers,
thalis


On Fri, 15 Jun 2001, Dariusz Pietrzak wrote:

> > It's done with CLUSTER indeed. Everything is copied in a temp table which is later renamed to the original table,
soall grant perimissions and indeces are lost on this table. Also keep in mind that you'll get new OIDs too (if you are
dependingon them) 
> Is very any way of going cluster without losing anything?
> At this point I am able to dump/restore database, but soon it'll become
> rather impossible for some time.
> Do I have to 'cluster' before putting any data in dbase?
>
>
>

> Clustering is really static i.e. it's done and after it any inserts/updates start spoiling the table again.
> So I guess the answer is no. Maybe you can create a procedure that does
> CLUSTER and then recreates the indeces and whatever else you lose in the
> process.

What a pity,
 I used to do some benchmarks and little studies using explain
and cluster had huge effect on efficency with data I used.
I thought it works like table partitions in oracle only within one data
location, pity.

Thanx.
--
Dariusz Pietrzak
Certified Nobody