Re: Conversion error of floating point numbers in pl/pgsql - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Conversion error of floating point numbers in pl/pgsql
Date
Msg-id CA+TgmoYRP=4DiMifGXLR76-ef4fmLoattBOxf3eVnnbvqQLzUQ@mail.gmail.com
Whole thread Raw
In response to Re: Conversion error of floating point numbers in pl/pgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Conversion error of floating point numbers in pl/pgsql  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
On Mon, Nov 16, 2015 at 9:49 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> writes:
>> Hello. I found that 9.5 has an undocumented difference from 9.4
>> in type cast in pl/pgsql and I think it might better be mentioned
>> as a change of behavior in release notes.
>
>> Whether do you think it is worth mentioning or not in release notes?
>
> This seems unnecessarily alarmist to me.  Anybody who's in the habit
> of converting between float4 and float8 will already be used to this
> behavior, because it is what has always happened everywhere else in
> the system.

Sure, but that doesn't mean nobody's functions will start behaving
differently.  It seems worth mentioning as a backward compatibility
issue to me, because if something breaks, it may not be immediately
obvious why it has gotten broken.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Parallel Seq Scan
Next
From: Robert Haas
Date:
Subject: Re: Foreign join pushdown vs EvalPlanQual