From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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-02 14:42:27 |
Message-ID: | 17878.1525272147@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Tue, May 1, 2018 at 12:08 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> 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.
> +1; this doesn't seem clear-cut and important enough to deviate from the
> (for me) preferable position of leaving well-enough-alone in the back
> branches.
Well, I seem to be in the minority here, so unless additional people
chime in, I'll revert this in the back branches shortly.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-05-02 14:47:09 | Re: BUG #15183: pg_upgrade and pg_upgrade.exe both corrupt sequences when migrating 9.1 10.3 |
Previous Message | Tom Lane | 2018-05-01 20:29:33 | Re: BUG #15180: Alter table add column if not exists with unique constraint will add extra duplicate |
From | Date | Subject | |
---|---|---|---|
Next Message | Hartmut Holzgraefe | 2018-05-02 14:48:39 | Re: Is a modern build system acceptable for older platforms |
Previous Message | Tom Lane | 2018-05-02 14:30:39 | Re: Optimize Arm64 crc32c implementation in Postgresql |