Tom Lane wrote: > However, this is really just cosmetic, as the dump is set up like this: > > SET default_tablespace = whatever; > CREATE TABLE whichever(...); > > If tablespace 'whatever' doesn't exist, you'll get an error on the SET > but the CREATE will succeed anyway. (I guess this only works cleanly > if the destination machine has *none* of the source's tablespaces, > else things might get assigned to unexpected tablespaces. But it's > definitely possible to restore a dump without having the same > tablespaces.)
Maybe it would be better if the dump has a RESET default_tablespace before the SET. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
