From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_migrator issues |
Date: | 2010-01-07 05:32:35 |
Message-ID: | 14677.1262842355@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
Perhaps we could compromise by calling it "--no-vacuum", instead?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2010-01-07 05:38:48 | Re: Testing with concurrent sessions |
Previous Message | Peter Eisentraut | 2010-01-07 05:30:29 | Re: Testing with concurrent sessions |