diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-01-02 12:01:14 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-01-02 12:01:14 -0300 |
| commit | cdbc0ca48ca96e5c787b1605ed2d6cf7407a5acf (patch) | |
| tree | f8e0e768c9d68dc79de634e35d10beb8f569039d /src/backend/utils/init/postinit.c | |
| parent | d194d7a52630d855f43edbf0129e131099af6c14 (diff) | |
| download | postgresql-cdbc0ca48ca96e5c787b1605ed2d6cf7407a5acf.tar.gz postgresql-cdbc0ca48ca96e5c787b1605ed2d6cf7407a5acf.zip | |
Fix background workers for EXEC_BACKEND
Commit da07a1e8 was broken for EXEC_BACKEND because I failed to realize
that the MaxBackends recomputation needed to be duplicated by
subprocesses in SubPostmasterMain. However, instead of having the value
be recomputed at all, it's better to assign the correct value at
postmaster initialization time, and have it be propagated to exec'ed
backends via BackendParameters.
MaxBackends stays as zero until after modules in
shared_preload_libraries have had a chance to register bgworkers, since
the value is going to be untrustworthy till that's finished.
Heikki Linnakangas and Álvaro Herrera
Diffstat (limited to 'src/backend/utils/init/postinit.c')
0 files changed, 0 insertions, 0 deletions