From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Vadim Trochinsky <me(at)vadim(dot)ws>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Table data exclusion patch for pg_dump |
Date: | 2009-05-01 19:50:29 |
Message-ID: | 22744.1241207429@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Well, you can shoot yourself in the foot using pg_restore's --use-list
> option too, but that doesn't mean it's not useful. And indeed it could
> be used to achieve the OP's ends, except that he would have spent
> useless time and space dumping the data for a table he doesn't want.
The critical difference, of course, being that when he discovers that it
doesn't work, he *has got* the data he needs to have to perform the
restore. Excluding data at dump time is considerably more dangerous
because of the likelihood that you won't have any recourse when you
need it.
(In which connection, it is an astonishingly bad idea to repurpose -d
and -D for this behavior, so soon after we deprecated them.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-05-01 19:54:22 | Re: Throw some low-level C scutwork at me |
Previous Message | Andrew Dunstan | 2009-05-01 19:45:16 | Re: Throw some low-level C scutwork at me |