postgresql/contrib/seg
Tom Lane c8314d62a9 Fix contrib/seg to be more wary of long input numbers.
seg stores the number of significant digits in an input number
in a "char" field.  If char is signed, and the input is more than
127 digits long, the count can read out as negative causing
seg_out() to print garbage (or, if you're really unlucky,
even crash).

To fix, clamp the digit count to be not more than FLT_DIG.
(In theory this loses some information about what the original
input was, but it doesn't seem like useful information; it would
not survive dump/restore in any case.)

Also, in case there are stored values of the seg type containing
bad data, add a clamp in seg_out's restore() subroutine.

Per bug #17725 from Robins Tharakan.  It's been like this
forever, so back-patch to all supported branches.

Discussion: https://postgr.es/m/17725-0a09313b67fbe86e@postgresql.org
2022-12-21 17:51:50 -05:00
..
data
expected Fix contrib/seg to be more wary of long input numbers. 2022-12-21 17:51:50 -05:00
sql Fix contrib/seg to be more wary of long input numbers. 2022-12-21 17:51:50 -05:00
.gitignore
Makefile
seg--1.0--1.1.sql
seg--1.1--1.2.sql
seg--1.1.sql
seg--1.2--1.3.sql
seg--unpackaged--1.0.sql
seg-validate.pl
seg.c Fix contrib/seg to be more wary of long input numbers. 2022-12-21 17:51:50 -05:00
seg.control
segdata.h
segparse.y Fix contrib/seg to be more wary of long input numbers. 2022-12-21 17:51:50 -05:00
segscan.l
sort-segments.pl