pgsql: Allow multiple tables to be specified in one VACUUM or ANALYZE c

Allow multiple tables to be specified in one VACUUM or ANALYZE command.

Not much to say about this; does what it says on the tin.

However, formerly, if there was a column list then the ANALYZE action was
implied; now it must be specified, or you get an error. This is because
it would otherwise be a bit unclear what the user meant if some tables
have column lists and some don't.

Nathan Bossart, reviewed by Michael Paquier and Masahiko Sawada, with some
editorialization by me

Discussion: https://postgr.es/m/E061A8E3-5E3D-494D-94F0-E8A9B312BBFC@amazon.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/11d8d72c27a64ea4e30adce11cf6c4f3dd3e60db

Modified Files
--------------
doc/src/sgml/ref/analyze.sgml | 14 ++-
doc/src/sgml/ref/vacuum.sgml | 36 ++++--
src/backend/commands/vacuum.c | 236 +++++++++++++++++++++++------------
src/backend/nodes/copyfuncs.c | 14 +++
src/backend/nodes/equalfuncs.c | 12 ++
src/backend/nodes/makefuncs.c | 15 +++
src/backend/parser/gram.y | 71 ++++-------
src/backend/postmaster/autovacuum.c | 20 +--
src/include/commands/vacuum.h | 3 +-
src/include/nodes/makefuncs.h | 2 +
src/include/nodes/nodes.h | 1 +
src/include/nodes/parsenodes.h | 22 +++-
src/test/regress/expected/vacuum.out | 23 +++-
src/test/regress/sql/vacuum.sql | 19 ++-
14 files changed, 329 insertions(+), 159 deletions(-)