mirror of
https://github.com/postgres/postgres.git
synced 2025-07-07 00:36:50 +03:00
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
This commit is contained in:
@ -510,7 +510,7 @@ SELECT '2006-08-13 12:34:56'::timestamptz;
|
||||
SET seq_page_cost TO 'NaN';
|
||||
ERROR: parameter "seq_page_cost" requires a numeric value
|
||||
SET vacuum_cost_delay TO '10s';
|
||||
ERROR: 10000 is outside the valid range for parameter "vacuum_cost_delay" (0 .. 100)
|
||||
ERROR: 10000 ms is outside the valid range for parameter "vacuum_cost_delay" (0 .. 100)
|
||||
SET geqo_selection_bias TO '-infinity';
|
||||
ERROR: -Infinity is outside the valid range for parameter "geqo_selection_bias" (1.5 .. 2)
|
||||
--
|
||||
|
Reference in New Issue
Block a user