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
List pgsql-hackers
I was looking at http://www.postgresql.org/docs/devel/static/bgworker.html with a client today.

It says:
"Unlike RegisterBackgroundWorker, which can only be called from within the postmaster,RegisterDynamicBackgroundWorker must be called from a regular backend."

Is that the correct restriction? In particular, don't we allow calling RegisterDynamicBackgroundWorker from another background worker? (In the launcher/worker kind of scenario, like AutoVacuum).

Also:
"Background workers are expected to be continuously running; if they exit cleanly, postgres will restart them immediately. "

This doesn't apply to dynamic ones, which we might want to clarify. Do we have a "term" for non-dynamic background workers? "static workers"?



--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

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