pgsql: Cleanup VACUUM option processing error messages - Mailing list pgsql-committers

From David Rowley
Subject pgsql: Cleanup VACUUM option processing error messages
Date
Msg-id E1v6xCy-000tIj-0v@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Cleanup VACUUM option processing error messages

The processing of the PARALLEL option for VACUUM was not quite
following what the DefElem code had intended.  defGetInt32() already has
code to handle missing parameters and returns a perfectly good error
message for when that happens.

Here we get rid of the ExecVacuum() error:

ERROR: parallel option requires a value between 0 and N

and leave defGetInt32() handle it, which will give:

ERROR:  parallel requires an integer value

defGetInt32() was already handling the non-integer parameter case, so it
may as well handle the missing parameter case too.

Additionally, parameterize the option name to make translator work easier,
and also use errhint_internal() rather than errhint() for the
BUFFER_USAGE_LIMIT option since there isn't any work for a translator to
do for "%s".

Author: David Rowley <dgrowleyml@gmail.com>
Reviewed-by: Álvaro Herrera <alvherre@kurilemu.de>
Reviewed-by: Masahiko Sawada <sawada.mshk@gmail.com>
Discussion: https://postgr.es/m/CAApHDvovH14tNWB+WvP6TSbfi7-=TysQ9h5tQ5AgavwyWRWKHA@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1b073cba4993b31fbf820504f297efce5d951c00

Modified Files
--------------
src/backend/commands/vacuum.c        | 42 ++++++++++++++----------------------
src/test/regress/expected/vacuum.out |  6 ++----
2 files changed, 18 insertions(+), 30 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Clean up memory leakage that occurs in context callback function
Next
From: Melanie Plageman
Date:
Subject: pgsql: Eliminate COPY FREEZE use of XLOG_HEAP2_VISIBLE