- Notifications
You must be signed in to change notification settings - Fork28
Commitb277057
committed
Fix broken Assert() introduced by 8e9a16ab8f7f0e58
Don't assert MultiXactIdIsRunning if the multi came from a tuple thathad been share-locked and later copied over to the new cluster bypg_upgrade. Doing that causes an error to be raised unnecessarily:MultiXactIdIsRunning is not open to the possibility that its argumentcame from a pg_upgraded tuple, and all its other callers are alreadychecking; but such multis cannot, obviously, have transactions stillrunning, so the assert is pointless.Noticed while investigating the bogus pg_multixact/offsets/0000 fileleft over by pg_upgrade, as reported by Andres Freund inhttp://www.postgresql.org/message-id/20140530121631.GE25431@alap3.anarazel.deBackpatch to 9.3, as the commit that introduced the buglet.1 parent1147035 commitb277057
1 file changed
+7
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5518 | 5518 | | |
5519 | 5519 | | |
5520 | 5520 | | |
| 5521 | + | |
| 5522 | + | |
| 5523 | + | |
| 5524 | + | |
5521 | 5525 | | |
5522 | | - | |
| 5526 | + | |
| 5527 | + | |
| 5528 | + | |
5523 | 5529 | | |
5524 | 5530 | | |
5525 | 5531 | | |
| |||
0 commit comments
Comments
(0)