The Hermit Hacker wrote:
> Or, modify pg_dump so that it auto-dumps to two files, one for schema, one
> for data. then its easier to modify the schema on a large database if
> tablespaces change ...
That's a pretty good idea as an option. But I'd say keep the schema
separate from the tablespace locations. And if you're going down that
path why not create a directory automatically and dump each table into a
separate file. On occasion I've had to restore one table by hand-editing
the pg_dump, and that's a real pain.