Re: Re: BUG #12885: The result of casting a double to an integer depends on the database version

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Pedro Gimeno <pgsql-004(at)personal(dot)formauri(dot)es>, rschaaf(at)commoninf(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: BUG #12885: The result of casting a double to an integer depends on the database version
Date: 2015-03-25 14:37:38
Message-ID: 3736.1427294258@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> On Wed, Mar 25, 2015 at 8:18 PM, Pedro Gimeno
> <pgsql-004(at)personal(dot)formauri(dot)es> wrote:
>> The only point of using copysign there was to deal with a negative zero
>> corner case. The attached removes copysign from the test program too,
>> relying instead on sprintf outputting the sign of minus zero when available.

> Cool, thanks. Applied to the code tree of Postgres, it gives the patch attached.

This is pretty desperately in need of some comments, but I'll see what
I can do with it.

I assume the consensus is that we should not back-patch this? It seems
like the kind of behavioral change that people might get annoyed about.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sékine Coulibaly 2015-03-25 15:06:17 Re: "no-slave yet" early CREATE TABLE transaction gets blocked when synchronous replication
Previous Message Kevin Grittner 2015-03-25 14:31:47 Re: "no-slave yet" early CREATE TABLE transaction gets blocked when synchronous replication