Re: Inaccurate results from numeric ln(), log(), exp() and pow()

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inaccurate results from numeric ln(), log(), exp() and pow()
Date: 2015-12-10 19:32:31
Message-ID: CA+Tgmoa3AgrvAiVT8ONz7UX8fz2PgXS4U8aRNEMrfo1JHOgDFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 10, 2015 at 2:25 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 10 December 2015 at 18:59, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Why did we make the change? I'm not sure it's bad, but
>>
>> it seems funny to whack a user-visible behavior around like this
>> without a clearly-explained reason.
>
> Surely the title of the post explains?

Nope. I'm not asking why we fixed the inaccurate results. I'm asking
why we now produce fewer output digits than before.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-12-10 19:39:36 Re: Patch: ResourceOwner optimization for tables with many partitions
Previous Message Andres Freund 2015-12-10 19:27:01 Re: Error with index on unlogged table