From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
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 02:56:18 |
Message-ID: | 31695.1494471378@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> On Thu, May 11, 2017 at 6:40 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The column list only matters for ANALYZE (or VACUUM ANALYZE). But yes,
>> it should be per-table.
> The grammar allows that by the way:
> =# VACUUM (full) aa (a);
> VACUUM
> Perhaps that's an oversight? I don't think it makes much sense.
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2017-05-11 03:10:15 | Re: [Proposal] Allow users to specify multiple tables in VACUUM commands |
Previous Message | Bruce Momjian | 2017-05-11 02:50:51 | Re: SCRAM in the PG 10 release notes |