On Wed, Nov 21, 2012 at 12:53 AM, Josh Kupershmidt <schmi...@gmail.com> wrote: > TBH, I didn't find the example above particularly compelling for > demonstrating the need for this feature. If you've just got one table > with dependent views which needs to be restored, it's pretty easy to > manually TRUNCATE and have pg_restore --data-only reload the table. > (And easy enough to combine the truncate and restore into a single > transaction in case anything goes wrong, if need be.) > > But I'm willing to grant that this proposed feature is potentially as > useful as existing restore-jiggering options like --disable-triggers. > And I guess I could see that if you're really stuck having to perform > a --data-only restore of many tables, this feature could come in > handy.
I think I would come down on the other side of this. We've never really been able to get --clean work properly in all scenarios, and it seems likely that a similar fate will befall this option. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
