aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2013-08-03 12:40:01 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2013-08-03 12:40:49 -0400
commit32b5a969e9f83866b2b1538e92bd6f1447ec6ac6 (patch)
tree5f2048d99afbf39eaefa6738baa07afb0b735d4f /src/backend/tcop/postgres.c
parent646b12115a81604fe083d555441d50c8967cee5f (diff)
downloadpostgresql-32b5a969e9f83866b2b1538e92bd6f1447ec6ac6.tar.gz
postgresql-32b5a969e9f83866b2b1538e92bd6f1447ec6ac6.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/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions