Re: Suggestion for --truncate-tables to pg_restore - Mailing list pgsql-hackers

From Karl O. Pinc
Subject Re: Suggestion for --truncate-tables to pg_restore
Date
Msg-id 1348377867.968.0@mofo
Whole thread Raw
In response to Re: Suggestion for --truncate-tables to pg_restore  ("Karl O. Pinc" <kop@meme.com>)
Responses Re: Suggestion for --truncate-tables to pg_restore  ("Karl O. Pinc" <kop@meme.com>)
List pgsql-hackers
Whoops.  Do over.  Sent the wrong file.

On 09/23/2012 12:19:07 AM, Karl O. Pinc wrote:
> On 09/21/2012 10:54:05 AM, Karl O. Pinc wrote:
> > On 09/20/2012 12:24:49 PM, Karl O. Pinc wrote:
> >
> > > I've had problems using pg_restore --data-only when
> > > restoring individual schemas (which contain data which
> > > has had bad things done to it).  --clean does not work
> > > well because of dependent objects in other schemas.
>
> Since there wasn't much more to do I've gone ahead
> and written the patch.  Works for me.
>
> Against git master.
> Passes regression tests, but there's no regression
> tests for pg_restore so this does not say much.
> Since there's no regression tests I've not written one.
>
> Since this is a real patch for application I've given
> it a new name (it's not a v2).
>
> Truncate done right before COPY, since that's what
> the parallel restores do.


Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein


Attachment

pgsql-hackers by date:

Previous
From: "Karl O. Pinc"
Date:
Subject: Re: Suggestion for --truncate-tables to pg_restore
Next
From: Kohei KaiGai
Date:
Subject: Re: [v9.3] writable foreign tables