From: | Christoph Dalitz <christoph(dot)dalitz(at)hs-niederrhein(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:27:50 |
Message-ID: | 20030128162750.72705c43.christoph.dalitz@hs-niederrhein.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 28 Jan 2003 10:19:23 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
>
What might be useful were some kind of quota (on the database
side, not the operating system) for a tablespace.
Any plans to implement something in that direction?
> We have no intention of changing over to Oracle-style disk space
> management, if that's what you were asking.
>
Ok, I see there is no reason to worry.
Christoph Dalitz
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Aufflick | 2003-01-28 15:29:55 | Re: all backends (pg7.2.3 / redhat 7.2) die due to unexpected signal 14 (SIGALRM) |
Previous Message | jhihn1 | 2003-01-28 15:19:36 |