[tamnd]

Summary

VACUUM and ANALYZE now run. rupg has no dead tuples to clean and no statistics to collect yet, so each statement does the checks of PostgreSQL and then ends. The checks are the options, the relations and the columns, and the result is the same errors, warnings and tags.

Changes

• rupg-session parses the options as ExecVacuum does. This includes BUFFER_USAGE_LIMIT, PARALLEL and INDEX_CLEANUP, and the errors for the options that cannot be used together.
• VACUUM cannot run in a transaction block, and it gives 25001 there. ANALYZE can run in a block.
• rupg-analyze adds vacuum_relations, which follows expand_vacuum_rel and vacuum_rel. It looks up all the relations first. It then gives the warning "skipping ... cannot vacuum non-tables or special system tables" or "cannot analyze ..." for a relation of the wrong kind. It checks the column list as validate_va_cols_list does.
• The extended protocol runs the statement too, with the same notices and positions.

Known differences

• No statistics go into pg_statistic, and VACUUM frees no space.
• VERBOSE gives no INFO output.
• The permission check always passes, because rupg has one superuser role.

Tests

connection/vacuum.test is the output of PostgreSQL 19 for the same script in a new database. fmt, clippy, the workspace tests and the checks of xtask pass on server1.