Re: Suggestion for --truncate-tables to pg_restore

Attached is version 2. The sgml did not build.

On 09/23/2012 12:24:27 AM, Karl O. Pinc wrote:
> 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(at)meme(dot)com>
> Free Software: "You don't pay back, you pay forward."
> -- Robert A. Heinlein
>
>

------quoted attachment------
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

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