Re: pg_migrator issues - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_migrator issues
Date
Msg-id 201001071212.o07CCk501262@momjian.us
Whole thread Raw
In response to Re: pg_migrator issues  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_migrator issues  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Tom Lane wrote:
> Peter Eisentraut <peter_e@gmx.net> writes:
> > On mån, 2010-01-04 at 13:07 -0500, Bruce Momjian wrote:
> >> Yea, I am not excited about having vacuumdb do only analyze, but it
> >> seems the most minimal solution.  I spelled it --only-analyze and just
> >> posted the reason and patch.
> 
> > I can't find the patch and the reason, but note that we already have
> > other options like --data-only, --schema-only, --tuples-only.  I
> > personally don't like the spelling of --only-analyze.
> 
> In particular note that pg_dump has options --schema and --schema-only,
> and nobody has complained about that.  I concur with Peter that this
> spelling is gratuitously unlike everyplace else.

Oh, interesting about pg_dump.  Let's just go with --analyze-only. 
--only-analyze is feeling odd to me too.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Leonardo F
Date:
Subject: Patch: Allow substring/replace() to get/set bit values
Next
From: Hiroshi Inoue
Date:
Subject: Re: libpq naming on Win64