- Notifications
You must be signed in to change notification settings - Fork38
Commit1a8aa64
committed
Setup SIGUSR1 procsignal_sigusr1_handler handler.
This is normally automatically done when a bgworker declares theBGWORKER_BACKEND_DATABASE_CONNECTION flag, but our bgworker doesn't connect todatabases, even though it calls InitPostgres, which will still initialize a newbacckend and thus participate to the ProcSignal infrastructure.This wasn't a problem until recently, but now that DROP DATABASE relies onPROCSIG_BARRIER to work on Windows (see commit4eb2176318d0561846c1f9fb3c68bede799d640f) we need to respond to ProcSignalnotifications.1 parent4761667 commit1a8aa64
1 file changed
+11
-0
lines changedLines changed: 11 additions & 0 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
339 | 339 |
| |
340 | 340 |
| |
341 | 341 |
| |
| 342 | + | |
| 343 | + | |
| 344 | + | |
| 345 | + | |
| 346 | + | |
| 347 | + | |
| 348 | + | |
342 | 349 |
| |
343 | 350 |
| |
| 351 | + | |
344 | 352 |
| |
345 | 353 |
| |
346 | 354 |
| |
| |||
379 | 387 |
| |
380 | 388 |
| |
381 | 389 |
| |
| 390 | + | |
| 391 | + | |
| 392 | + | |
382 | 393 |
| |
383 | 394 |
| |
384 | 395 |
| |
|
0 commit comments
Comments
(0)