Hi,
On 2018-01-03 20:17:04 -0500, Tom Lane wrote:
> So this patch has been in place for two weeks, the buildfarm has still
> got the measles, and we're entering the January commitfest with a lot
> of other work to get done. I realize that the two weeks were mostly
> holiday time, but it's time to have some urgency about clearing the
> buildfarm failures.
Agreed.
> As best I understand, the remaining failures simply arise from
> an unstable regression test case and aren't teaching us anything
> of value.
I think that's the correct interpretation.
> I propose that for the moment, we simply remove the
> failing query from join.sql. We can put it back when there's
> reason to think it will pass everywhere.
Alternatively we could temporarily push an alternative output. It
doesn't seem inconceivable we missed an actual bug due to the
noise. Don't have a strong opinion on which of the two to choose.
Unless somebody does something first, I'll disable the test tomorrow
pacific morning. But perhaps Thomas can up with an approach till then
that seems likely to pass on the different architectures. Seems quite
possible to just adjust the thresholds carefully?
Greetings,
Andres Freund
