From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mark Wong <mark(at)2ndquadrant(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: buildfarm animal shoveler failing with "Illegal instruction" |
Date: | 2020-10-02 01:12:53 |
Message-ID: | 1118017.1601601173@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Mark Wong <mark(at)2ndquadrant(dot)com> writes:
> I'm getting Tom set up with access too, in case he has time before me to
> get a stack trace to see what's happening...
tl;dr: it's hard to conclude that this is anything but a compiler bug.
I was able to reproduce this on shoveler's host, but only when using
the compiler shoveler uses (clang-3.9), not the 6.3 gcc that's also
on there and is of similar vintage. Observations:
* You don't need any complicated test case; "pg_dump template1"
is enough.
* Reverting 1ed6b8956's addition of a "postfix operators are not supported
anymore" warning to dumpOpr() makes it go away. This despite the fact
that that code is never reached when dumping template1. (We do enter
dumpOpr, but the oprinfo->dobj.dump test always fails.)
* Reducing the optimization level to -O1 or -O0 makes it go away.
* Inserting a debugging fprintf in dumpOpr makes it go away.
Since clang 3.9 is several years old, maybe we could move shoveler
up to a newer version? Or dial it down to -O1 optimization?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2020-10-02 01:21:02 | Re: New statistics for tuning WAL buffer size |
Previous Message | James Coleman | 2020-10-02 01:10:23 | Re: enable_incremental_sort changes query behavior |