Re: PostmasterContext survives into parallel workers!? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: PostmasterContext survives into parallel workers!?
Date
Msg-id 20160801225435.jgltryqui3cca2xh@alap3.anarazel.de
Whole thread Raw
In response to Re: PostmasterContext survives into parallel workers!?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PostmasterContext survives into parallel workers!?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2016-08-01 18:28:44 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2016-08-01 18:09:03 -0400, Robert Haas wrote:
> >> (Also vaguely on the list of things to clean up: can't we make it so
> >> that bgworkers aren't launched from inside a signal handler?  Blech.)
> 
> > Isn't pretty much everything on-demand below postmaster started from a
> > signal handler?
> 
> I think it depends.  As an example, maybe_start_bgworker is called
> from PostmasterMain, *and* from ServerLoop, *and* from reaper,
> *and* from sigusr1_handler.  That's likely excessive, but it's what
> we've got at the moment.

Personally I think the whole logic should be reworked so we do most of
that that only from one place. Especially the signal handler stuff
should imo just be replaced by setting latch, which then does the work
inside the normal main loop.

Andres



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: PostmasterContext survives into parallel workers!?
Next
From: Tom Lane
Date:
Subject: Re: PostmasterContext survives into parallel workers!?