> 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
Well ,as long as we have the file per object layout it probably makes sense
have "speaking paths", But I see no real problem with:
RELATIONOID standing for whatever the consensus will be.
I do not really see an argument for using a tablespaceoid instead of
it's [maybe mangled] name.
pgsql-hackers by date
|Next:||From: Zeugswetter Andreas SB||Date: 2000-06-27 13:39:13|
|Subject: AW: SQL99 functions |
|Previous:||From: Peter Mount||Date: 2000-06-27 11:38:40|
|Subject: RE: Proposal: More flexible backup/restore via pg_dump |