Re: BUG #8355: PL/Python 3 can't convert infinity to PostgreSQL's value - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #8355: PL/Python 3 can't convert infinity to PostgreSQL's value
Date
Msg-id 4679.1375548434@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #8355: PL/Python 3 can't convert infinity to PostgreSQL's value  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
I wrote:
> ... But it seems like maybe we had better cover the
> following cases that we do not cover today:

>     inf
>     +inf
>     -inf
>     +Infinity

I've committed a patch that makes sure float4in and float8in accept
these spellings even when the underlying strtod(3) function does not.
However, it turns out that this doesn't fix your test case on my HPUX
box, and I'm betting that it won't help on Windows either, because
it's actually Python that's failing.  You can reproduce the failure
without any Postgres code involved at all:

$ python
Python 2.5.1 (r251:54863, Jul 12 2007, 23:25:33)
[GCC 2.95.3 20010315 (release)] on hp-ux10
Type "help", "copyright", "credits" or "license" for more information.
>>> a = float('inf')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: invalid literal for float(): inf

Now, I seriously doubt that the Python guys will give a darn about
a 15-year-old version of HPUX, but if you can reproduce the above
on your Windows machine, I'd suggest filing a bug about it with them.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: [HACKERS] 9.3beta2: Failure to pg_upgrade
Next
From: jbglaw@lug-owl.de
Date:
Subject: BUG #8361: 9.3~beta2-2: Wrong `interval' format with aggregate functions.