From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_migrator issues |
Date: | 2010-01-07 12:12:46 |
Message-ID: | 201001071212.o07CCk501262@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > On mn, 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2010-01-07 12:21:53 | Re: libpq naming on Win64 |
Previous Message | Leonardo F | 2010-01-07 12:02:16 | Patch: Allow substring/replace() to get/set bit values |