From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: a raft of parallelism-related bug fixes |
Date: | 2016-02-21 18:05:23 |
Message-ID: | 30385.1456077923@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Feb 8, 2016 at 2:36 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>> I have no problem running any test cases you wish on a branch in a loop for
>> the next week and reporting back any errors.
> Well, what I've done is push into the buildfarm code that will allow
> us to do *the most exhaustive* testing that I know how to do in an
> automated fashion. Which is to create a file that says this:
> force_parallel_mode=regress
> max_parallel_degree=2
I did a few dozen runs of the core regression tests with those settings
(using current HEAD plus my lockGroupLeaderIdentifier-ectomy patch).
Roughly one time in ten, it fails in the stats test, with diffs as
attached. I interpret this as meaning that parallel workers don't
reliably transmit stats to the stats collector, though maybe there
is something else happening.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
regression.diffs | text/x-diff | 1.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2016-02-21 18:17:51 | Re: pgsql: Cosmetic improvements in new config_info code. |
Previous Message | Tom Lane | 2016-02-21 17:45:36 | Re: Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl |