=?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <postgres(at)cybertec(dot)at> writes:
> how would you handle table spaces?
The plan that's been discussed simply defines a tablespace as being a
directory somewhere; physical storage of individual tables would remain
basically the same, one or more files under the containing directory.
The point of this being, of course, that the DBA could create the
tablespace directories on different partitions or volumes in order to
provide the behavior he wants.
In my mind this would be primarily a cleaner, more flexible
reimplementation of the existing "database location" feature.
regards, tom lane