forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit360abc0
committed
Be sure to release proc->backendLock after SetupLockInTable() failure.
The various places that transferred fast-path locks to the main lock tableneglected to release the PGPROC's backendLock if SetupLockInTable faileddue to being out of shared memory. In most cases this is no big deal sinceensuing error cleanup would release all held LWLocks anyway. But there aresome hot-standby functions that don't consider failure ofFastPathTransferRelationLocks to be a hard error, and in those cases thisoversight could lead to system lockup. For consistency, make all of theseplaces look the same as FastPathTransferRelationLocks.Noted while looking for the cause of Dan Wood's bugs --- this wasn't it,but it's a bug anyway.1 parentc357be2 commit360abc0
1 file changed
+3
-0
lines changedLines changed: 3 additions & 0 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
2537 | 2537 |
| |
2538 | 2538 |
| |
2539 | 2539 |
| |
| 2540 | + | |
2540 | 2541 |
| |
2541 | 2542 |
| |
2542 | 2543 |
| |
| |||
2592 | 2593 |
| |
2593 | 2594 |
| |
2594 | 2595 |
| |
| 2596 | + | |
2595 | 2597 |
| |
2596 | 2598 |
| |
2597 | 2599 |
| |
| |||
4055 | 4057 |
| |
4056 | 4058 |
| |
4057 | 4059 |
| |
| 4060 | + | |
4058 | 4061 |
| |
4059 | 4062 |
| |
4060 | 4063 |
| |
|
0 commit comments
Comments
(0)