Re: intermittent failures in Cygwin from select_parallel tests

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: intermittent failures in Cygwin from select_parallel tests
Date: 2017-08-03 14:45:50
Message-ID: CA+TgmoZV3pDkhLEUmo+1ubTWVKv=61maHTtWf0u4J+PGcQGMjw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 2, 2017 at 11:47 PM, Noah Misch <noah(at)leadboat(dot)com> wrote:
> postmaster algorithms rely on the PG_SETMASK() calls preventing that. Without
> such protection, duplicate bgworkers are an understandable result. I caught
> several other assertions; the PMChildFlags failure is another case of
> duplicate postmaster children:
>
> 6 TRAP: FailedAssertion("!(entry->trans == ((void *)0))", File: "pgstat.c", Line: 871)
> 3 TRAP: FailedAssertion("!(PMSignalState->PMChildFlags[slot] == 1)", File: "pmsignal.c", Line: 229)
> 20 TRAP: FailedAssertion("!(RefCountErrors == 0)", File: "bufmgr.c", Line: 2523)
> 21 TRAP: FailedAssertion("!(vmq->mq_sender == ((void *)0))", File: "shm_mq.c", Line: 221)
> Also, got a few "select() failed in postmaster: Bad address"
>
> I suspect a Cygwin signals bug. I'll try to distill a self-contained test
> case for the Cygwin hackers. The lack of failures on buildfarm member brolga
> argues that older Cygwin is not affected.

Nice detective work.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2017-08-03 15:45:34 Re: Macros bundling RELKIND_* conditions
Previous Message Robert Haas 2017-08-03 14:43:25 Re: reload-through-the-top-parent switch the partition table