Include GUC's unit, if it has one, in out-of-range error messages.
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 10 Mar 2019 17:18:17 +0000 (13:18 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 10 Mar 2019 17:18:17 +0000 (13:18 -0400)
commit28a65fc3607a0f45c39a9418f747459bb4f1592a
treeb52cead932456b520410353fa0c5e90312c8760a
parentac75959cdc073a09a0d3d649fb922d90e1df4c61
Include GUC's unit, if it has one, in out-of-range error messages.

This should reduce confusion in cases where we've applied a units
conversion, so that the number being reported (and the quoted range
limits) are in some other units than what the user gave in the
setting we're rejecting.

Some of the changes here assume that float GUCs can have units,
which isn't true just yet, but will be shortly.

Discussion: https://postgr.es/m/3811.1552169665@sss.pgh.pa.us
src/backend/utils/misc/guc.c
src/test/regress/expected/guc.out