mirror of
https://github.com/postgres/postgres.git
synced 2025-07-08 11:42:09 +03:00
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
This commit is contained in:
@ -611,3 +611,18 @@ makeGroupingSet(GroupingSetKind kind, List *content, int location)
|
||||
n->location = location;
|
||||
return n;
|
||||
}
|
||||
|
||||
/*
|
||||
* makeVacuumRelation -
|
||||
* create a VacuumRelation node
|
||||
*/
|
||||
VacuumRelation *
|
||||
makeVacuumRelation(RangeVar *relation, Oid oid, List *va_cols)
|
||||
{
|
||||
VacuumRelation *v = makeNode(VacuumRelation);
|
||||
|
||||
v->relation = relation;
|
||||
v->oid = oid;
|
||||
v->va_cols = va_cols;
|
||||
return v;
|
||||
}
|
||||
|
Reference in New Issue
Block a user