forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commite2ce9aa
committed
Never crash-and-restart for bgworkers without shared memory access.
The motivation for a crash and restart cycle when a backend dies isthat it might have corrupted shared memory on the way down; and wecan't recover reliably except by reinitializing everything. But thatdoesn't apply to processes that don't touch shared memory. Currently,there's nothing to prevent a background worker that doesn't requestshared memory access from touching shared memory anyway, but that's aseparate bug.Previous to this commit, the coding in postmaster.c was inconsistent:an exit status other than 0 or 1 didn't provoke a crash-and-restart,but failure to release the postmaster child slot did. This changemakes those cases consistent.1 parent1891b41 commite2ce9aa
1 file changed
+10
-10
lines changedLines changed: 10 additions & 10 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
2864 | 2864 |
| |
2865 | 2865 |
| |
2866 | 2866 |
| |
2867 |
| - | |
2868 | 2867 |
| |
2869 |
| - | |
2870 |
| - | |
2871 |
| - | |
2872 |
| - | |
2873 |
| - | |
2874 |
| - | |
2875 |
| - | |
2876 |
| - | |
2877 |
| - | |
| 2868 | + | |
| 2869 | + | |
| 2870 | + | |
| 2871 | + | |
| 2872 | + | |
| 2873 | + | |
| 2874 | + | |
| 2875 | + | |
| 2876 | + | |
| 2877 | + | |
2878 | 2878 |
| |
2879 | 2879 |
| |
2880 | 2880 |
| |
|
0 commit comments
Comments
(0)