|From:||Simon Riggs <simon(at)2ndquadrant(dot)com>|
|To:||Stephen Frost <sfrost(at)snowman(dot)net>|
|Cc:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, daveg <daveg(at)sonic(dot)net>, pgsql-patches(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>|
|Subject:||Re: pg_dump additional options for performance|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Mon, 2008-07-21 at 07:56 -0400, Stephen Frost wrote:
> * Simon Riggs (simon(at)2ndquadrant(dot)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
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
|Next Message||Peter Eisentraut||2008-07-23 17:08:53||Re: pltcl_*mod commands are broken on Solaris 10|
|Previous Message||Tom Lane||2008-07-23 16:38:47||Re: Do we really want to migrate plproxy and citext into PG core distribution?|
|Next Message||Simon Riggs||2008-07-23 17:09:47||Re: pg_dump additional options for performance|
|Previous Message||Tom Lane||2008-07-23 16:05:36||Re: [PATCHES] GIN improvements|