Fix range check in ECPG numeric to int conversion
authorJohn Naylor <[email protected]>
Fri, 30 Jul 2021 17:50:23 +0000 (13:50 -0400)
committerJohn Naylor <[email protected]>
Fri, 30 Jul 2021 20:34:33 +0000 (16:34 -0400)
commitcfcb0ceabde11dc6bf57185f72a2b14132631dfd
tree143dd66348eb0e0692b8133ed1fd66c71c02a017
parent32d182dd0da9628a4bc1515b69694d6e361a8de4
Fix range check in ECPG numeric to int conversion

The previous coding guarded against -INT_MAX instead of INT_MIN,
leading to -2147483648 being rejected as out of range.

Per bug #17128 from Kevin Sweet

Discussion: https://www.postgresql.org/message-id/flat/17128-55a8a879727a3e3a%40postgresql.org
Reviewed-by: Tom Lane
Backpatch to all supported branches
doc/src/sgml/ecpg.sgml
src/interfaces/ecpg/pgtypeslib/numeric.c
src/interfaces/ecpg/test/expected/pgtypeslib-num_test.c
src/interfaces/ecpg/test/expected/pgtypeslib-num_test.stderr
src/interfaces/ecpg/test/expected/pgtypeslib-num_test.stdout
src/interfaces/ecpg/test/pgtypeslib/num_test.pgc