Re: AW: Big 7.1 open items - Mailing list pgsql-hackers

From Tom Lane
Subject Re: AW: Big 7.1 open items
Date
Msg-id 9572.962115828@sss.pgh.pa.us
Whole thread Raw
In response to AW: Big 7.1 open items  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
List pgsql-hackers
Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.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
IMHO.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: SQL99 functions
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: Proposal: More flexible backup/restore via pg_dump