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

Nathan Bossart <bossartn@amazon.com>

From: "Bossart, Nathan" <bossartn@amazon.com>

To: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Cc: Robert Haas <robertmhaas@gmail.com>, Michael Paquier <michael.paquier@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Masahiko Sawada <sawada.mshk@gmail.com>

Date: 2017-05-18T23:24:41Z

Lists: pgsql-hackers

Attachments

vacuum_multiple_tables_v5.patch (application/octet-stream) patch v5

Thanks all for your feedback.  I’ve attached v5 of the patch.

Changes:
 - fixed implicit declaration of ‘attnameAttNum’ in vacuum.c
 - specified relations and columns are de-duplicated
 - users are now forced to specify ANALYZE if a column list is given
 - added to VACUUM regression test
 - rebased with master

Nathan

Commits

Allow multiple tables to be specified in one VACUUM or ANALYZE command.
- 11d8d72c27a6 11.0 landed
Give a better error for duplicate entries in VACUUM/ANALYZE column list.
- ea31541f5648 9.6.6 landed
- e56facd8b300 9.2.24 landed
- b572b435ca67 9.4.15 landed
- a2b1eb23496e 10.0 landed
- a09d8be7ddaf 9.3.20 landed
- 71480501057f 11.0 landed
- 122289a66b92 9.5.10 landed
Reject ANALYZE commands during VACUUM FULL or another ANALYZE.
- e415b469b33b 9.5.0 cited