|
31 | 31 |
|
32 | 32 | <para> |
33 | 33 | Background workers can be initialized at the time that |
34 | | - <productname>PostgreSQL</> is started including the module name in |
| 34 | + <productname>PostgreSQL</> is startedbyincluding the module name in |
35 | 35 | <varname>shared_preload_libraries</>. A module wishing to run a background |
36 | 36 | worker can register it by calling |
37 | 37 | <function>RegisterBackgroundWorker(<type>BackgroundWorker *worker</type>)</function> |
@@ -179,10 +179,10 @@ typedef struct BackgroundWorker |
179 | 179 | When a background worker is registered using the |
180 | 180 | <function>RegisterDynamicBackgroundWorker</function> function, it is |
181 | 181 | possible for the backend performing the registration to obtain information |
182 | | - the status of the worker. Backends wishing to do this should pass the |
183 | | - address of a <type>BackgroundWorkerHandle *</type> as the second argument |
184 | | - to <function>RegisterDynamicBackgroundWorker</function>. If the worker |
185 | | - is successfully registered, this pointer will be initialized with an |
| 182 | +regardingthe status of the worker. Backends wishing to do this should |
| 183 | +pass theaddress of a <type>BackgroundWorkerHandle *</type> as the second |
| 184 | +argumentto <function>RegisterDynamicBackgroundWorker</function>. If the |
| 185 | +workeris successfully registered, this pointer will be initialized with an |
186 | 186 | opaque handle that can subsequently be passed to |
187 | 187 | <function>GetBackgroundWorkerPid(<parameter>BackgroundWorkerHandle *</parameter>, <parameter>pid_t *</parameter>)</function>. |
188 | 188 | This function can be used to poll the status of the worker: a return |
|