Michael Paquier <michael.paqu...@gmail.com> writes: > On Mon, Apr 18, 2016 at 12:31 PM, Peter Eisentraut <pete...@gmx.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
