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

Nathan Bossart <bossartn@amazon.com>

View thread View on postgr.es

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

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

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

Date: 2017-05-17T22:38:10Z

Lists: pgsql-hackers

Attachments

vacuum_multiple_tables_v4.patch (application/octet-stream) patch v4

I’ve attached a v4 of the patch.

Changes:
 - Early in vacuum(…), emit an ERROR if any specified columns do not exist.
 - Emit a WARNING and skip any specified tables or columns that disappear before they are actually processed.
 - Small additions to the 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