Re: Review: Extra Daemons / bgworker
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Markus Wanner <markus@bluegap.ch>, kaigai@kaigai.gr.jp, PostgreSQL-development Hackers <pgsql-hackers@postgresql.org>
Date: 2012-12-05T22:30:24Z
Lists: pgsql-hackers
On 5 December 2012 22:22, Andres Freund <andres@2ndquadrant.com> wrote: > 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? Just clarifying how it worked, for the docs; happy with the way it is. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services