Re: [HACKERS] intermittent failures in Cygwin from select_paralleltests - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [HACKERS] intermittent failures in Cygwin from select_paralleltests
Date
Msg-id d0faf818-ca6e-795b-52bc-33250d120ee9@2ndQuadrant.com
Whole thread Raw
In response to Re: [HACKERS] intermittent failures in Cygwin from select_parallel tests  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [HACKERS] intermittent failures in Cygwin from select_parallel tests
List pgsql-hackers

On 06/26/2017 10:36 AM, Amit Kapila wrote:
> On Fri, Jun 23, 2017 at 9:12 AM, Andrew Dunstan
> <andrew.dunstan@2ndquadrant.com> wrote:
>>
>> On 06/22/2017 10:24 AM, Tom Lane wrote:
>>> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>>>> Please let me know if there are tests I can run. I  missed your earlier
>>>> request in this thread, sorry about that.
>>> That earlier request is still valid.  Also, if you can reproduce the
>>> symptom that lorikeet just showed and get a stack trace from the
>>> (hypothetical) postmaster core dump, that would be hugely valuable.
>>>
>>>
>>
>> See attached log and stacktrace
>>
> Is this all the log contents or is there something else?  The attached
> log looks strange to me in the sense that the first worker that gets
> invoked is Parallel worker number 2 and it finds that somebody else
> has already set the sender handle.
>



No, it's the end of the log file. I can rerun and get the whole log file
if you like.

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: [HACKERS] Optional message to user when terminating/cancellingbackend
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] fix empty array expression in get_qual_for_list()