Re: Review: Extra Daemons / bgworker

Andres Freund <andres@2ndquadrant.com>

From: Andres Freund <andres@2ndquadrant.com>

To: Alvaro Herrera <alvherre@2ndquadrant.com>

Cc: Simon Riggs <simon@2ndQuadrant.com>, Markus Wanner <markus@bluegap.ch>, kaigai@kaigai.gr.jp, PostgreSQL-development Hackers <pgsql-hackers@postgresql.org>

Date: 2012-12-05T22:22:54Z

Lists: pgsql-hackers

On 2012-12-05 19:03:44 -0300, Alvaro Herrera wrote:
> Simon Riggs wrote:
> > Prefer
> > BgWorkerStart_ConsistentState to be renamed to BgWorkerRun_InHotStandby
> > BgWorkerStart_RecoveryFinished to be renamed to BgWorkerRun_InNormalMode
> >
> > presumably a process will shutdown if (BgWorkerRun_InHotStandby &&
> > !BgWorkerRun_InNormalMode)
>
> Hmm, no, I haven't considered that.  You mean that a bgworker that
> specifies to start at BgWorkerStart_ConsistentState will stop once
> normal mode is reached?  Currently they don't do that.  And since we
> don't have the notion that workers stop working, it wouldn't work --
> postmaster would start them back up immediately.

I personally don't see too much demand for this from a use-case
perspective. Simon, did you have anything in mind that made you ask
this?

Greetings,

Andres Freund

--
 Andres Freund	                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services