At 09:55 23/06/00 +1000, Chris Bitmead wrote:
>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.
>
Have a look at my message entitled:
Proposal: More flexible backup/restore via pg_dump
It's supposed to address these issues.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
