Dynamic background workers & docs question - Mailing list pgsql-hackers

From Magnus Hagander
Subject Dynamic background workers & docs question
Date
Msg-id CABUevEwfE+FQvTCDwOJCOn2b7KdOaiV4PRdipgYzaSYN8bxUAw@mail.gmail.com
Whole thread Raw
Responses Re: Dynamic background workers & docs question  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
<div dir="ltr">I was looking at <a
href="http://www.postgresql.org/docs/devel/static/bgworker.html">http://www.postgresql.org/docs/devel/static/bgworker.html</a>
witha client today.<br /><br />It says:<br />"Unlike RegisterBackgroundWorker, which can only be called from within the
postmaster,RegisterDynamicBackgroundWorkermust be called from a regular backend."<br /><br />Is that the correct
restriction?In particular, don't we allow calling RegisterDynamicBackgroundWorker from another background worker? (In
thelauncher/worker kind of scenario, like AutoVacuum).<br /><br />Also:<br />"Background workers are expected to be
continuouslyrunning; if they exit cleanly, postgres will restart them immediately. "<br /><br />This doesn't apply to
dynamicones, which we might want to clarify. Do we have a "term" for non-dynamic background workers? "static
workers"?<br/><br /><br /><br />--<br /> Magnus Hagander<br /> Me: <a
href="http://www.hagander.net/">http://www.hagander.net/</a><br/>  Work: <a
href="http://www.redpill-linpro.com/">http://www.redpill-linpro.com/</a><br/></div> 

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: About adding a column to system catalog pg_attribute
Next
From: Heikki Linnakangas
Date:
Subject: Only first XLogRecData is visible to rm_desc with WAL_DEBUG