Re: pg_dump additional options for performance

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, daveg <daveg(at)sonic(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: pg_dump additional options for performance
Date: 2008-07-21 11:56:02
Message-ID: 20080721115602.GG18846@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Simon,

* 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.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2008-07-21 13:46:55 Re: overlaps performance
Previous Message Stephen Frost 2008-07-21 11:54:16 Re: pg_dump additional options for performance

Browse pgsql-patches by date

  From Date Subject
Next Message Tatsuo Ishii 2008-07-21 14:04:50 WITH RECUSIVE patches 0721
Previous Message Stephen Frost 2008-07-21 11:54:16 Re: pg_dump additional options for performance