|
34 | 34 | <productname>PostgreSQL</productname> is started by including the module name in
|
35 | 35 | <varname>shared_preload_libraries</varname>. A module wishing to run a background
|
36 | 36 | worker can register it by calling
|
37 |
| - <function>RegisterBackgroundWorker(<type>BackgroundWorker *worker</type>)</function> |
38 |
| - from its <function>_PG_init()</function>. Background workers can also be started |
39 |
| - after the system is up and running by calling the function |
40 |
| - <function>RegisterDynamicBackgroundWorker(<type>BackgroundWorker |
41 |
| - *worker, BackgroundWorkerHandle **handle</type>)</function>. Unlike |
42 |
| - <function>RegisterBackgroundWorker</function>, which can only be called from within |
43 |
| - the postmaster, <function>RegisterDynamicBackgroundWorker</function> must be |
44 |
| - called from a regular backend or another background worker. |
| 37 | + <function>RegisterBackgroundWorker(<type>BackgroundWorker</type> |
| 38 | + *<parameter>worker</parameter>)</function> |
| 39 | + from its <function>_PG_init()</function> function. |
| 40 | + Background workers can also be started |
| 41 | + after the system is up and running by calling |
| 42 | + <function>RegisterDynamicBackgroundWorker(<type>BackgroundWorker</type> |
| 43 | + *<parameter>worker</parameter>, <type>BackgroundWorkerHandle</type> |
| 44 | + **<parameter>handle</parameter>)</function>. Unlike |
| 45 | + <function>RegisterBackgroundWorker</function>, which can only be called from |
| 46 | + within the postmaster process, |
| 47 | + <function>RegisterDynamicBackgroundWorker</function> must be called |
| 48 | + from a regular backend or another background worker. |
45 | 49 | </para>
|
46 | 50 |
|
47 | 51 | <para>
|
|
0 commit comments