From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Noah Misch <noah(at)leadboat(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Add trigonometric functions that work in degrees. |
Date: | 2016-04-19 03:56:55 |
Message-ID: | 32425.1461038215@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Noah Misch <noah(at)leadboat(dot)com> writes:
> On Mon, Apr 18, 2016 at 10:22:59PM -0400, Tom Lane wrote:
>> We could alternatively set extra_float_digits to its max value and hope
>> that off-by-one-in-the-last-place values would get printed as something
>> visibly different from the exact result. I'm not sure I want to trust
>> that that works reliably; but maybe it would be worth printing the
>> result both ways, just to provide additional info when there's a failure.
> We'd have an independent problem if extra_float_digits=3 prints the same
> digits for distinguishable float values, so I wouldn't mind relying on it not
> to do that. But can we expect the extra_float_digits=3 representation of
> those particular values to be the same for every implementation?
Hm? The expected answer is exact (30, 45, or whatever) in each case.
If we get some residual low-order digits then it's a failure, so we don't
need to worry about whether it's the same failure everywhere.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2016-04-19 04:16:31 | Re: [COMMITTERS] pgsql: Add trigonometric functions that work in degrees. |
Previous Message | Noah Misch | 2016-04-19 02:49:50 | Re: [COMMITTERS] pgsql: Add trigonometric functions that work in degrees. |
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2016-04-19 04:14:02 | Re: Optimization for updating foreign tables in Postgres FDW |
Previous Message | Etsuro Fujita | 2016-04-19 03:45:39 | Re: Optimization for updating foreign tables in Postgres FDW |