Re: pg_dump exclusion switches and functions/types

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Csaba Nagy <nagy@ecircle-ag.com>
Cc: Kris Jurka <books@ejurka.com>, postgres hackers <pgsql-hackers@postgresql.org>
Date: 2006-10-06T17:22:25Z
Lists: pgsql-hackers
Csaba Nagy <nagy@ecircle-ag.com> writes:
> Would it be reasonable to include one more switch: 'include
> dependencies' ?

We are two months past feature freeze ... adding entirely new features
to pg_dump is *not* on the table for 8.2.  What we need to do at the
moment is make sure that the features we've got work sanely and won't
create headaches for likely future extensions; but not actually
implement those extensions.

> The scenario I most care about is to be able to make a complete data
> base dump (including non-schema objects) while excluding only a few
> tables.

Isn't this the same as Kris' complaint?  Why do you need additional
dependency analysis to do the above?

			regards, tom lane