summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJohn Naylor <john.naylor@postgresql.org>2021-07-30 13:50:23 -0400
committerJohn Naylor <john.naylor@postgresql.org>2021-07-30 16:18:59 -0400
commit171bf1cea579ce11bc7f0b2986f052022f2b6be1 (patch)
tree7e2c318bfaf975d675371ecff54b32798e217e54 /doc
parent41d27ee7b870c1a1213704d3c020a01eb55799b0 (diff)
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
Diffstat (limited to 'doc')
-rw-r--r--doc/src/sgml/ecpg.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index 7266e229a47..84df3c3868c 100644
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -8666,7 +8666,7 @@ int dectoint(decimal *np, int *ip);
Note that the ECPG implementation differs from the <productname>Informix</productname>
implementation. <productname>Informix</productname> limits an integer to the range from -32767 to
32767, while the limits in the ECPG implementation depend on the
- architecture (<literal>-INT_MAX .. INT_MAX</literal>).
+ architecture (<literal>INT_MIN .. INT_MAX</literal>).
</para>
</listitem>
</varlistentry>