| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christoph Dalitz <christoph(dot)dalitz(at)hs-niederrhein(dot)de> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Francisco Reyes <lists(at)natserv(dot)com>, PG Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Status of tablespaces |
| Date: | 2003-01-28 15:19:23 |
| Message-ID: | 13184.1043767163@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Christoph Dalitz <christoph(dot)dalitz(at)hs-niederrhein(dot)de> writes:
> What are the plans for Postgres tablespaces?
Well, what I envision is only a cleaner reimplementation of the
existing LOCATION facility: the DBA will be able to designate certain
directories as tablespaces and then assign individual tables, indexes,
etc to particular tablespaces. Presumably, the DBA places each
tablespace directory on a different disk (otherwise there's not much
point in the exercise), and then the arrangement lets him control what
lives where.
We have no intention of changing over to Oracle-style disk space
management, if that's what you were asking.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jhihn1 | 2003-01-28 15:19:36 | |
| Previous Message | Ron Johnson | 2003-01-28 15:15:09 | Re: Indexing foreign keys |