Bruce Momjian <[EMAIL PROTECTED]> writes:
> I was thinking we could have a var like schema search path that
> specifies where we try to create the object:
> SET tablespace_path = 'tblspc1, pg_default';
> CREATE TABLE test(x int);
> This combines the idea of pulling the TABLESPACE specification out of
> the CREATE, and allows a fallback if the primary tablespace doesn't
> exist.
... and takes us even further away from the notion that the default
tablespace is determined by the parent object (database or schema).
I think that we have a clean, understandable, easy-to-use tablespace
behavior now, and we should not muck it up for abstract second-order
goals like having portable dumps for databases that were created
unportably in the first place.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
