Re: Current master hangs under the debugger after Parallel Seq Scan (Linux, MacOS) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Current master hangs under the debugger after Parallel Seq Scan (Linux, MacOS)
Date
Msg-id 1615736.1743003537@sss.pgh.pa.us
Whole thread Raw
In response to Current master hangs under the debugger after Parallel Seq Scan (Linux, MacOS)  (Vladlen Popolitov <v.popolitov@postgrespro.ru>)
Responses Re: Current master hangs under the debugger after Parallel Seq Scan (Linux, MacOS)
List pgsql-hackers
Vladlen Popolitov <v.popolitov@postgrespro.ru> writes:
> d) Above query will start parallel worker(s). When worker(s) finish(es),
> it/they send SIGUSR1 that is caught by debugger. When you dimiss
> the signal message, you find that query continues to run, but really it
> waits (in latch.c or in waiteventset.c depending on commit version).

I'm fairly skeptical of this.  IME, when you see something like that,
the actual problem is that the debugger has failed to pass the signal
on to the program-under-test.

> I tracked this behaviour down to commit
> commit 7202d72787d3b93b692feae62ee963238580c877

... and that raises my skepticism to stratospheric levels, because
that commit did exactly nothing that would have changed runtime
behavior.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset
Next
From: Robert Haas
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset