Re: [Proposal] Allow users to specify multiple tables in VACUUM commands

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [Proposal] Allow users to specify multiple tables in VACUUM commands
Date: 2017-05-18 15:38:53
Message-ID: CAD21AoAT10M6FPc0u2rub-7yw=Ynm7ENE9DNw-eTU01EQ40Hfg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 19, 2017 at 12:03 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Ugh, really? Are we sure that the current behavior is anything other
>> than a bug? The idea that VACUUM foo (a) implies ANALYZE doesn't
>> really sit very well with me in the first place. I'd be more inclined
>> to reject that with an ERROR complaining that the column list can't be
>> specified except for ANALYZE.
>
> Yeah, that's probably more sensible. I think the rationale was "if you
> specify columns you must want the ANALYZE option, so why make you type
> that in explicitly?". But I can see the argument that it's likely to
> confuse users who might have a weaker grasp of the semantics.
>

I'd not known such VACUUM behavior so I was a bit surprised but
considering consistency with current behavior I thought that is not
bad idea. But complaining with error seems more sensible.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marina Polyakova 2017-05-18 16:00:09 Re: WIP Patch: Precalculate stable functions, infrastructure v1
Previous Message Noah Misch 2017-05-18 15:11:37 Re: Get stuck when dropping a subscription during synchronizing table