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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "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-11 05:05:14
Message-ID: CAB7nPqTA4k6naGjnZ9Z-UNPwc+EhQRcrY+jH93z8pGhUnJuUhg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 11, 2017 at 11:56 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It would be hard to reject at the grammar level, and not very friendly
> either because you'd only get "syntax error". We could certainly make
> the runtime code throw an error if you gave a column list without saying
> ANALYZE. But on the other hand, why bother? I do not remember ever
> seeing a question that boiled down to somebody being confused by this.

The docs also say that adding a column list implies an ANALYZE even if
other keywords are added, and that's the case. Sorry for the noise.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-05-11 05:32:32 Re: logical replication deranged sender
Previous Message Kyotaro HORIGUCHI 2017-05-11 04:09:20 Re: Duplicate usage of tablespace location?