That's really nifty! I didn't know you could do that! So I expanded it, and I grepped for that UUID through the 46 gig file, and I found the row in the dump that shouldn't be there... It defies explanation.
--- On Thu, 12/10/09, John R Pierce <pie...@hogranch.com> wrote: > From: John R Pierce <pie...@hogranch.com> > Subject: Re: [GENERAL] pg_dump and ON DELETE CASCADE problem > To: cgg...@yahoo.com, pgsql-general@postgresql.org > Date: Thursday, December 10, 2009, 3:29 PM > CG wrote: > > Thanks for the suggestion. I'm not sure what you mean > when you say I should restore to a file. Do you mean I > should dump the database to an SQL file instead of the > "compressed" format? > > > > he meant... > > pg_restore -f outputfile.sql > yourdumpfile > > this will convert the dumpfile to SQL... > > > > > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
