Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> writes:
> I do not really see an argument for using a tablespaceoid instead of
> it's [maybe mangled] name.
Eliminating filesystem-based restrictions on names, for one.
For example we'd not have to forbid slashes and (probably) backquotes
in tablespace names if we did this, and we'd not have to worry about
filesystem-induced limits on name lengths. Renaming a tablespace
would also be trivial instead of nigh impossible.
It might be that using tablespace names as directory names is worth
enough from the admin point of view to make the above restrictions
acceptable. But it's a tradeoff, and not one with an obvious choice
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2000-06-27 14:48:53|
|Subject: Re: AW: Proposal: More flexible backup/restore via pg_dump |
|Previous:||From: Tom Lane||Date: 2000-06-27 14:14:37|
|Subject: Re: SQL99 functions |