Re: BUG #15091: to_number() returns incorrect value - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15091: to_number() returns incorrect value
Date
Msg-id 6272.1520016092@sss.pgh.pa.us
Whole thread Raw
In response to RE: BUG #15091: to_number() returns incorrect value  (Michael Aiello <michael.aiello@asg.com>)
List pgsql-bugs
Michael Aiello <michael.aiello@asg.com> writes:
> Could you let me know whether this issue will be addressed by a bug fix, and if so which version(s) would be targeted
andabout how long it will take? 

[ shrug... ] There is no proposed patch, nor has anyone offered to create
one, so that's an unanswerable question at the moment.  If we had a patch
we could evaluate how invasive it is and how big the behavioral change
would be exactly, and then decide whether to back-patch.  But my suspicion
is that we would not back-patch, but only change it in the next major
release.  This is the sort of thing where somebody might be relying on the
current behavior as "correct" and not be happy if it changes under them in
a minor release.

            regards, tom lane


pgsql-bugs by date:

Previous
From: Michael Aiello
Date:
Subject: RE: BUG #15091: to_number() returns incorrect value
Next
From: Andrew Gierth
Date:
Subject: Re: TO_DATE Function unintended behavior when month value is greater than 12