Re: pg_dump additional options for performance - Mailing list pgsql-patches

From Simon Riggs
Subject Re: pg_dump additional options for performance
Date
Msg-id 1216831237.3894.676.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: pg_dump additional options for performance  (Stephen Frost <sfrost@snowman.net>)
Responses Re: pg_dump additional options for performance
List pgsql-patches
On Mon, 2008-07-21 at 07:56 -0400, Stephen Frost wrote:
> Simon,
>
> * Simon Riggs (simon@2ndquadrant.com) wrote:
> > > I hadn't realized that Simon was using "pre-schema" and "post-schema"
> > > to name the first and third parts.  I'd agree that this is confusing
> > > nomenclature: it looks like it's trying to say that the data is the
> > > schema, and the schema is not!  How about "pre-data and "post-data"?
> >
> > OK by me. Any other takers?
>
> Having the command-line options be "--schema-pre-data" and
> "--schema-post-data" is fine with me.  Leaving them the way they are is
> also fine by me.  It's the documentation (back to pg_dump.sgml,
> ~774/~797) that starts talking about Pre-Schema and Post-Schema.

OK, Mr.Reviewer, sir:

* patch redone using --schema-before-data and --schema-after-data

* docs rewritten using short clear descriptions using only the words
"before" and "after", like in the option names

* all variable names changed

* retested

So prefixes "pre" and "post" no longer appear anywhere. No latin derived
phrases, just good ol' Anglo-Saxon words.

--
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support

Attachment

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] WITH RECUSIVE patches 0723
Next
From: Simon Riggs
Date:
Subject: Re: pg_dump additional options for performance