Re: power() function in Windows: "value out of range: underflow"

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Huong Dangminh <huo-dangminh(at)ys(dot)jp(dot)nec(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Akio Iwaasa <aki-iwaasa(at)vt(dot)jp(dot)nec(dot)com>
Subject: Re: power() function in Windows: "value out of range: underflow"
Date: 2018-05-01 19:08:46
Message-ID: CA+TgmoY+3v2h7=odvxQPO_NzyupFSBv7Y1OhzhPPa9bQ5b9OWg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Tue, May 1, 2018 at 1:49 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The point here, I think, is that you get behavior X on approximately 100%
> of modern platforms, but (without this patch) behavior Y on some number of
> older platforms. People who have tested their app on a modern platform
> and then find that it misbehaves on an old one will think this is a bug
> fix. People who only run their app on an old platform may think the
> pre-patch behavior is fine, in which case they will indeed be upset if
> we change it in a minor release. Are there more of the latter than the
> former? I don't really know, and you don't either.

I agree with all of that.

> But I don't think
> we should discount the existence of the former category. Deploying
> to production on an older release of $system than you develop on
> is hardly an unusual scenario.

That's probably true, but making dev, test, and production boxes
similar is generally good practice and users can do as much or as
little of it as they find they need in order to avoid getting burned.
They can't do anything about behavior changes we inject into minor
releases.

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2018-05-01 19:24:27 Re: BUG #15180: Alter table add column if not exists with unique constraint will add extra duplicate
Previous Message Tom Lane 2018-05-01 18:47:41 Re: BUG #15180: Alter table add column if not exists with unique constraint will add extra duplicate

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-05-01 19:24:42 Re: Should we add GUCs to allow partition pruning to be disabled?
Previous Message Robert Haas 2018-05-01 18:58:42 Re: [HACKERS] Clock with Adaptive Replacement