| From: | "Thalis A(dot) Kalfigopoulos" <thalis(at)cs(dot)pitt(dot)edu> |
|---|---|
| To: | Dariusz Pietrzak <dariush(at)ajax(dot)umcs(dot)lublin(dot)pl> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: CLUSTER. (fwd) |
| Date: | 2001-06-15 15:59:40 |
| Message-ID: | Pine.LNX.4.21.0106151157110.19889-100000@aluminum.cs.pitt.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
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, so all grant perimissions and indeces are lost on this table. Also keep in mind that you'll get new OIDs too (if you are depending on 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?
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gunnar Rønning | 2001-06-15 16:02:46 | The bytea datatype and JDBC |
| Previous Message | Dariusz Pietrzak | 2001-06-15 15:49:16 | Re: CLUSTER. (fwd) |