Re: pg_dump additional options for performance

Stephen Frost <[email protected]> Mon, 21 Jul 2008 17:00:57 -0400
Newsgroups gmane.comp.db.postgresql.devel.patches
Message-ID <[email protected]>
Tom, et al,

* Tom Lane ([email protected]) wrote:
> Ah, I see.  No objection to those switch names, at least assuming we
> want to stick to positive-logic switches.  What did you think of the
> negative-logic suggestion (--omit-xxx)?

My preference is for positive-logic switches in general.  The place
where I would use this patch would lend itself to being more options if
--omit-xxxx were used.  I expect that would hold true for most people.
It would be:

  --omit-data --omit-post-load
  --omit-pre-load --omit-post-load
  --omit-pre-load --omit-data

vs.

  --schema-pre-load
  --data-only
  --schema-post-load

Point being that I'd be dumping these into seperate files where I could
more easily manipulate the pre-load or post-load files.  I'd still want
pre/post load to be seperate though since this would be used in cases
where there's alot of data (hence the reason for the split) and putting
pre and post together and running them before data would slow things
down quite a bit.

Are there use cases for just --omit-post-load or --omit-pre-load?
Probably, but I just don't see any situation where I'd use them like
that.

	Thanks,

		Stephen
signature.asc (application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkiE+QkACgkQrzgMPqB3kigkGACgi8uKZAdC+4jSb8HLXMCKX5pB
tL0AniL8b92uIWZ1o94Qz+gOOJpyAEa4
=D2GS
-----END PGP SIGNATURE-----