forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commitf66885b
committed
Allow special SKIP LOCKED condition in Assert()
Under concurrency, it is possible for two sessions to be merrily lockingand releasing a tuple and marking it again as HEAP_XMAX_INVALID all thewhile a third session attempts to lock it, miserably fails at it, andthen contemplates life, the universe and everything only to eventuallyfail an assertion that said bit is not set. Before SKIP LOCKED that wasindeed a reasonable expectation, but alas! commitdf630b0 falsifiedit.This bug is as old as time itself, and even older, if you think timebegins with the oldest supported branch. Therefore, backpatch to allsupported branches.Author: Simon Riggs <simon.riggs@enterprisedb.com>Discussion:https://postgr.es/m/CANbhV-FeEwMnN8yuMyss7if1ZKjOKfjcgqB26n8pqu1e=q0ebg@mail.gmail.com1 parent56a3e84 commitf66885b
1 file changed
+9
-1
lines changedLines changed: 9 additions & 1 deletion
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
4751 | 4751 |
| |
4752 | 4752 |
| |
4753 | 4753 |
| |
4754 |
| - | |
| 4754 | + | |
| 4755 | + | |
| 4756 | + | |
| 4757 | + | |
| 4758 | + | |
| 4759 | + | |
| 4760 | + | |
| 4761 | + | |
| 4762 | + | |
4755 | 4763 |
| |
4756 | 4764 |
| |
4757 | 4765 |
| |
|
0 commit comments
Comments
(0)