|From:||"Karl O(dot) Pinc" <kop(at)meme(dot)com>|
|Subject:||Re: Suggestion for --truncate-tables to pg_restore|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Attached is version 3.
The convention seems to be to leave the operator at the
end of the line when breaking long lines, so do that.
Add extra () -- make operator precedence explicit and
have indentation reflect operator precedence.
On 09/23/2012 08:52:07 PM, Karl O. Pinc wrote:
> On 09/23/2012 12:24:27 AM, Karl O. Pinc wrote:
> > 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.
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
|Next Message||Karl O. Pinc||2012-10-17 02:50:25||Doc patch, put commas in the right place in pg_restore docs|
|Previous Message||Josh Berkus||2012-10-16 22:03:53||Re: [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility|