Re: How to REINDEX in high volume environments?

Just wanted to pipe in here. I am still very interested in tablespaces ( I have many database systems that are over
500GB and growing) and am willing to port my tablespace patch to 7.4. I have everything (but only tested here) working
in 7.2 but the patch was not accepted. I didn't see a great speed improvement but the patch helps with storage management.

Recap. the patch would enable the following

a database to have a default data tablespace and index tablespace
a user to have a default data and index tablespace
a table to have a specific tablespace
an index to have a specfic tablespace

I would like to also add namespace (schema) to have a default data and index tablespaces

Jim

> Justin Clift <justin(at)postgresql(dot)org> writes:
> > Shridhar Daithankar wrote:
> >> Looks like we should have a subdirectory in database directory which stores
> >> index.
>
> > That was my first thought also, but an alternative/additional approach
> > would be this (not sure if it's workable):
>
> See the tablespaces TODO item. I'm not excited about building
> half-baked versions of tablespaces before we get around to doing the
> real thing ...
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html