aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2013-08-03 12:39:57 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2013-08-03 12:40:45 -0400
commit6084c0705ae03fa7641369e33a2c487585b8f942 (patch)
tree7e320bd3f5d86af16634e3b17de1a9aff7a9cbfb /src/backend/executor/nodeFunctionscan.c
parentc928dc9dfbbfa374f8614726428743d4445bc1d7 (diff)
downloadpostgresql-6084c0705ae03fa7641369e33a2c487585b8f942.tar.gz
postgresql-6084c0705ae03fa7641369e33a2c487585b8f942.zip
Make sure float4in/float8in accept all standard spellings of "infinity".
The C99 and POSIX standards require strtod() to accept all these spellings (case-insensitively): "inf", "+inf", "-inf", "infinity", "+infinity", "-infinity". However, pre-C99 systems might accept only some or none of these, and apparently Windows still doesn't accept "inf". To avoid surprising cross-platform behavioral differences, manually check for each of these spellings if strtod() fails. We were previously handling just "infinity" and "-infinity" that way, but since C99 is most of the world now, it seems likely that applications are expecting all these spellings to work. Per bug #8355 from Basil Peace. It turns out this fix won't actually resolve his problem, because Python isn't being this careful; but that doesn't mean we shouldn't be.
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions