Re: "stuck spinlock" - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "stuck spinlock"
Date
Msg-id 25316.1386957249@sss.pgh.pa.us
Whole thread Raw
In response to Re: "stuck spinlock"  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: "stuck spinlock"
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> I wonder what to do about bgworker's bgworker_die()? I don't really see
> how that can be fixed without breaking the API?

IMO it should be flushed and bgworkers should use the same die() handler
as every other backend, or else one like the one in worker_spi, which just
sets a flag for testing later.  If we try to change the signal handling
contracts, 80% of backend code will be unusable in bgworkers, which is not
where we want to be I think.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: patch: make_timestamp function
Next
From: Andres Freund
Date:
Subject: Re: "stuck spinlock"