From: | Pedro Gimeno <pgsql-004(at)personal(dot)formauri(dot)es> |
---|---|
To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Rounding to even for numeric data type |
Date: | 2015-04-22 12:30:52 |
Message-ID: | 5537947C.9060904@personal.formauri.es |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dean Rasheed wrote, On 2015-03-28 10:01:
> On 28 March 2015 at 05:16, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
>>>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>>
>> Tom> I think the concern over backwards compatibility here is probably
>> Tom> overblown; but if we're sufficiently worried about it, a possible
>> Tom> compromise is to invent a numeric_rounding_mode GUC, so that
>> Tom> people could get back the old behavior if they really care.
>>
>> I only see one issue with this, but it's a nasty one: do we really want
>> to make all numeric operations that might do rounding stable rather than
>> immutable?
>>
>
> Yeah, making all numeric functions non-immutable seems like a really bad idea.
Would it be possible to make it an unchangeable per-cluster or
per-database setting, kinda like how encoding behaves? Wouldn't that
allow to keep the functions immutable?
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-04-22 12:46:35 | Re: Rounding to even for numeric data type |
Previous Message | Michael Paquier | 2015-04-22 12:10:59 | Re: Improve sleep processing of pg_rewind TAP tests |