aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_utilcmd.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2013-08-03 12:39:47 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2013-08-03 12:40:27 -0400
commit221e92f64c6e136e550ec2592aac3ae0d4623209 (patch)
tree532d32b3047c89812d4835f1e734bce7e0a4ae87 /src/backend/parser/parse_utilcmd.c
parent706f9dd914c64a41e06b5fbfd62d6d6dab43eeb8 (diff)
downloadpostgresql-221e92f64c6e136e550ec2592aac3ae0d4623209.tar.gz
postgresql-221e92f64c6e136e550ec2592aac3ae0d4623209.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/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions