From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Add trigonometric functions that work in degrees. |
Date: | 2016-04-18 13:17:46 |
Message-ID: | 12238.1460985466@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> On Mon, Apr 18, 2016 at 12:31 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> I don't know if it's worth tracking this as an open item and thus
>> kind-of release blocker if no one else has the problem. But I
>> definitely still have it. My initial suspicion was that this had
>> something to do with a partial upgrade to gcc 6 (not yet released), in
>> other words a messed up system. But I was able to reproduce it in a
>> freshly installed chroot. It only happens with various versions of gcc,
>> but not with clang. So I'm going to have to keep digging.
> gcc is moving slowly but surely to have 6.0 in a released state btw:
> https://gcc.gnu.org/ml/gcc/2016-04/msg00103.html
Given that it's apparently showing the results of asind as NULL, the
theory that comes to mind is some sort of optimization issue affecting
the output tuple's null-flags. I have no idea why only this test would
be affected, though. Anyway, a good way to test that theory would be
to see if the -O level affects it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2016-04-18 14:12:32 | Re: pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
Previous Message | Robert Haas | 2016-04-18 11:34:34 | Re: pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-04-18 13:17:51 | Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE. |
Previous Message | Kevin Grittner | 2016-04-18 12:31:10 | Re: snapshot too old, configured by time |