Re: Table spaces (was Re: State of Beta 2)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
Cc: PgSQL General ML <pgsql-general(at)postgresql(dot)org>
Subject: Re: Table spaces (was Re: State of Beta 2)
Date: 2003-09-15 14:54:22
Message-ID: 10376.1063637662@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> writes:
> On Sun, 2003-09-14 at 23:08, Tom Lane wrote:
>> Yeah, that's been in the back of my mind also. Once we have tablespaces
>> and a couple of the other basic features we're still missing, it might
>> be a more reasonable proposition to freeze the on-disk representation.

> I think that every effort should be made so that the on-disk struct-
> ure (ODS) doesn't have to change when tablespaces is implemented.

That's not going to happen --- tablespaces will be complex enough
without trying to support a backwards-compatible special case.

If we have a workable pg_upgrade by the time tablespaces happen, it
would be reasonable to expect it to be able to rearrange the user data
files of an existing installation into the new directory layout. If
we don't, the issue is moot anyway.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2003-09-15 14:58:37 Re: Initalizing PostgreSQL Database
Previous Message Cott Lang 2003-09-15 14:41:11 Re: [PERFORM] best arrangement of 3 disks for (insert)