Обсуждение: rebuild index question

Поиск
Список
Период
Сортировка

rebuild index question

От
"Glenn Wiorek"
Дата:
Hello all,  It appears that the rebuild index command (driven by contrib/reindexdb)  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 (again) 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 everyone working around this?
 
For that matter how are folks dealing with  laying out large databases across multiple drives?? 
 
Thanks,
Glenn

Re: rebuild index question

От
Bruno Wolff III
Дата:
On Thu, Oct 16, 2003 at 14:28:09 -0500,
  Glenn Wiorek <gwiorek@jmlafferty.com> wrote:
> Hello all,  It appears that the rebuild index command (driven by contrib/reindexdb)  recreates the index with a new
oidsin the default data directory. This has just caused me a lot of grief to move and relink 329 indices (again)
becauseof space and disk constraints (35 GB to spread across 4 drives).  Since rebuilding indexes is a common and often
neededtask how is everyone working around this?  

This should be a lot better in 7.4. Most people should not need to do
reindexes.

Re: rebuild index question

От
Tom Lane
Дата:
"Glenn Wiorek" <gwiorek@jmlafferty.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