Re: jitflags in _outPlannedStmt and _readPlannedStmt treated as bool type

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: jitflags in _outPlannedStmt and _readPlannedStmt treated as bool type
Date: 2018-04-28 22:33:45
Message-ID: 31748.1524954825@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> On Sat, Apr 28, 2018 at 18:23 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Actually, I was about to ask whether you guys had changed anything about
>> dory's configuration recently. It's now had eight consecutive passes
>> since I put in 63ca350 last night. Given its record before that, just
>> about one failure in every three tries, the odds of that are less than 4%
>> if I'm counting on my fingers correctly. So I'm wondering what changed;
>> and more change might not be what we want.

> I’m not aware of any change today. I’ve asked when the last change was
> made.

If in fact nothing's been changed, then the run of successes is probably
just rotten luck. (Either that or it's a Heisenbug, and the addition
of a VirtualQuery call made it go away. Ugh.) In that case I'm on board
with putting it into a continuous-rebuild loop till we get some failures.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2018-04-28 23:16:59 Re: [HACKERS] Clock with Adaptive Replacement
Previous Message Kefan Yang 2018-04-28 22:31:21 RE: GSoC 2018: Sorting Algorithm and Benchmarking