pgsql: Fix the usage of parallel and full options of vacuum command.

From: Amit Kapila <akapila(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix the usage of parallel and full options of vacuum command.
Date: 2020-04-16 05:38:02
Message-ID: E1jOxDu-00058X-Gr@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix the usage of parallel and full options of vacuum command.

Earlier we were inconsistent in allowing the usage of parallel and
full options. Change it such that we disallow them only when they are
combined in a way that we don't support.

In passing, improve the comments in some of the existing tests of parallel
vacuum.

Reported-by: Tushar Ahuja
Author: Justin Pryzby, Amit Kapila
Reviewed-by: Sawada Masahiko, Michael Paquier, Mahendra Singh Thalor and
Amit Kapila
Discussion: https://postgr.es/m/58c8d171-e665-6fa3-a9d3-d9423b694dae%40enterprisedb.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/24d2d38b1eb86c0b410ad0f07f66566a83c6f05c

Modified Files
--------------
doc/src/sgml/ref/vacuum.sgml | 32 ++++++++++++++++----------------
src/backend/commands/vacuum.c | 6 ++----
src/test/regress/expected/vacuum.out | 6 ++++--
src/test/regress/sql/vacuum.sql | 5 ++++-
4 files changed, 26 insertions(+), 23 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2020-04-16 18:46:19 pgsql: Fix cache reference leak in contrib/sepgsql.
Previous Message Michael Paquier 2020-04-16 05:19:03 pgsql: Disable silently generation of manifests with servers <= 12 in p