Re: Storage Location Patch Proposal for V7.3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: jim(at)buttafuoco(dot)net, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Storage Location Patch Proposal for V7.3
Date: 2002-03-05 07:30:07
Message-ID: 13961.1015313407@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I think Jim has some very good points here. What does his
> implementation lack?

Forward compatibility to a future tablespace implementation.
If we do this, we'll be stuck with supporting this feature set,
not to mention this syntax; neither of which have garnered any
support from the assembled hackers.

I went back to look at TODO.detail/tablespaces, and find that it's
badly in need of editing. Much of the discussion there is
back-and-forthing about the question of naming files by OID,
which is now a done deal. But it is clear that people wanted to
have a notion of tablespaces as objects somewhat orthogonal to
databases. I didn't see any support for hard-wiring tablespace
assignments on the basis of "tables here, indexes there", either.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2002-03-05 07:45:26 Cache invalidation notification (was: Database Caching)
Previous Message Bruce Momjian 2002-03-05 06:52:02 Re: elog() patch