Re: Big 7.1 open items

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
Subject: Re: Big 7.1 open items
Date: 2000-06-27 21:16:49
Message-ID: 200006272116.RAA09578@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Mikheev, Vadim writes:
> >> Do we need *both* database & tablespace to find table file ?!
> >> Imho, database shouldn't be used...
>
> > Then the system tables from different databases would collide.
>
> I've been assuming that we would create a separate tablespace for
> each database, which would be the location of that database's
> system tables. It's probably also the default tablespace for user
> tables created in that database, though it wouldn't have to be.
>
> There should also be a known tablespace for the installation-wide tables
> (pg_shadow et al).
>
> With this approach tablespace+relation would indeed be a sufficient
> identifier. We could even eliminate the knowledge that certain
> tables are installation-wide from the bufmgr and below (currently
> that knowledge is hardwired in places that I'd rather didn't know
> about it...)

Well, if we did that, I can see a good reason to not use per-database
directories in the tablepspace.

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-06-27 21:19:31 Re: Big 7.1 open items
Previous Message Tom Lane 2000-06-27 21:05:49 Re: Is *that* why debugging backend startup is so hard!?