aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-05-29 15:19:07 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2017-05-29 15:19:07 -0400
commitce509452955487c9e11d042b6a564c76600334db (patch)
tree81dd619b688487e697cb1b1d4ceb934b3d11ff01 /src/backend/utils/adt/jsonfuncs.c
parentdced55dafead62cfff81a3fedb35acd8e32c9b02 (diff)
downloadpostgresql-ce509452955487c9e11d042b6a564c76600334db.tar.gz
postgresql-ce509452955487c9e11d042b6a564c76600334db.zip
Allow NumericOnly to be "+ FCONST".
The NumericOnly grammar production accepted ICONST, + ICONST, - ICONST, FCONST, and - FCONST, but for some reason not + FCONST. This led to strange inconsistencies like regression=# set random_page_cost = +4; SET regression=# set random_page_cost = 4000000000; SET regression=# set random_page_cost = +4000000000; ERROR: syntax error at or near "4000000000" (because 4000000000 is too large to be an ICONST). While there's no actual functional reason to need to write a "+", if we allow it for integers it seems like we should allow it for numerics too. It's been like that forever, so back-patch to all supported branches. Discussion: https://postgr.es/m/30908.1496006184@sss.pgh.pa.us
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions