Chander Ganesan <chander@xxxxxxxxxx> writes: > I'd like to suggest that a feature be added to pg_dumpall to remove > tablespace definitions/creation from the output. While the inclusion is > important for backups - it's equally painful when attempting to migrate > data from a development to production database. Since PostgreSQL won't > create the directory that will contain the tablespace, the tablespace > creation will fail. Following that, any objects that are to be created > in that tablespace will fail (since the tablespace doesn't exist). If the above statements were actually true, it'd be a problem, but they are not true. The dump only contains "SET default_tablespace = foo" commands, which may themselves fail, but they won't prevent subsequent CREATE TABLE commands from succeeding. regards, tom lane
