> > Do we need *both* database & tablespace to find table file ?!
> > Imho, database shouldn't be used...
> That'd work fine for me, but I think Bruce was arguing for paths that
> included the database name. We'd end up with paths that go something
> (plus some kind of decoration for segment and version), so you'd have
> a hard time telling which files in a tablespace belong to which
> database. Doesn't bother me a whole lot, personally --- if one wants
We could create /data/databases/DATABASEOID/ and create soft-links to
table-files. This way different tables of the same database could be in
different tablespaces. /data/database path would be used in production
and /data/tablespace path would be used in recovery.
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2000-06-26 22:33:56|
|Subject: Re: 'natural join' core dump |
|Previous:||From: Jenni Jaeger||Date: 2000-06-26 22:13:43|
|Subject: connection to Access tables|