|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Christoph Berg <myon(at)debian(dot)org>|
|Cc:||PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Unstable select_parallel regression output in 12rc1|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Christoph Berg <myon(at)debian(dot)org> writes:
> Re: Tom Lane 2019-09-26 <12685(dot)1569510771(at)sss(dot)pgh(dot)pa(dot)us>
>> We haven't seen it in quite some time in HEAD, though I fear that's
>> just due to bad luck or change of timing of unrelated tests.
> The v13 package builds that are running every 6h here haven't seen a
> problem yet either, so the probability of triggering it seems very
> low. So it's not a pressing problem.
I've pushed some changes to try to ameliorate the issue.
> (There's some extension modules
> where the testsuite fails at a much higher rate, getting all targets
> to pass at the same time is next to impossible there :(. )
I feel your pain, believe me. Used to fight the same kind of problems
when I was at Red Hat. Are any of those extension modules part of
regards, tom lane
|Next Message||Jeff Davis||2019-09-28 17:36:45||Re: max_parallel_workers question|
|Previous Message||Tom Lane||2019-09-28 17:34:19||Re: Instability of partition_prune regression test results|