> Peter Eisentraut <peter_e@gmx.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@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026