-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> Well, notwithstanding my well known love of perl, that strikes me as
> spending a pound to save a penny. And custom format dumps rock ;-) Also,
> your recipe above is buggy, BTW. A CREATE INDEX statement might well not
> be the first item in the post-data section.
>
> But we could also add these switches to pg_dump too if people feel it's
> worthwhile. I haven't looked but the logic should not be terribly hard.
A big +1 to --pre-data and --post-data, but until we get there, or
if you have an existing dump file (schema *or* schema+data) that needs
parsing, there is an existing tool:
http://blog.endpoint.com/2010/01/splitting-postgres-pgdump-into-pre-and.html
Once these new flags and the ability to custom format dump pg_dumpall
is done, I'll have very little left to complain about with pg_dump :)
- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201108271855
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAk5ZdfwACgkQvJuQZxSWSsipDQCgpmNtD/I/2gfAzm2b3jouD8nS
qhgAn33t5VLiF8HeslBwCqyMzQJy6VN5
=PfK7
-----END PGP SIGNATURE-----
