| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Glenn Wiorek" <gwiorek(at)jmlafferty(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: rebuild index question |
| Date: | 2003-10-17 00:25:28 |
| Message-ID: | 16979.1066350328@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Glenn Wiorek" <gwiorek(at)jmlafferty(dot)com> writes:
> Hello all, It appears that the rebuild index command (driven by contrib/re=
> indexdb) recreates the index with a new oids in the default data directory=
> . This has just caused me a lot of grief to move and relink 329 indices (ag=
> ain) because of space and disk constraints (35 GB to spread across 4 drives=
> ). Since rebuilding indexes is a common and often needed task how is every=
> one working around this?=20
Manually moving and symlinking tables has always been a painful
alternative. That's why there's interest in building a tablespace
feature to supplant it. In the meantime, I think you're stuck.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Reeves | 2003-10-17 02:09:15 | Postgresql having trouble serving over 1000 connections |
| Previous Message | Robert W. Kernell | 2003-10-16 22:47:51 | Which Group??? |