Thread: pgsql: Fix range check in ECPG numeric to int conversion

pgsql: Fix range check in ECPG numeric to int conversion

From

John Naylor

Date:

30 July 2021, 20:43:22

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/5fcf3945bd90bb0170938ad780159779367dc8ac

Modified Files
--------------
doc/src/sgml/ecpg.sgml                              |  2 +-
src/interfaces/ecpg/pgtypeslib/numeric.c            |  7 ++++++-
.../ecpg/test/expected/pgtypeslib-num_test.c        | 21 ++++++++++++++++-----
.../ecpg/test/expected/pgtypeslib-num_test.stderr   |  2 +-
.../ecpg/test/expected/pgtypeslib-num_test.stdout   |  2 ++
src/interfaces/ecpg/test/pgtypeslib/num_test.pgc    | 13 ++++++++++++-
6 files changed, 38 insertions(+), 9 deletions(-)