lost lock during toasting allows fk violation

back to CI dashboard

2 patchsets tracked - current t253223_4

v4t253223_4posted Aug 05, 16:44never appliedrecent 18dpg 20apply failed
v3t253223_3posted Jul 29, 04:00successsupersededrecent 16dpg 20
basebf80a4c2d Aug 07, 05:52 on master
applyapplied Aug 07, 06:14
rebaselast tried about 15 hours ago on f20c42783
Applying: Fix loss of tuple lock during TOAST step in heap_update()
Using index info to reconstruct a base tree...
M	src/backend/access/heap/heapam.c
M	src/test/isolation/isolation_schedule
Falling back to patching base and 3-way merge...
Auto-merging src/test/isolation/isolation_schedule
CONFLICT (content): Merge conflict in src/test/isolation/isolation_schedule
Auto-merging src/backend/access/heap/heapam.c
Patch failed at 0001 Fix loss of tuple lock during TOAST step in heap_update()

error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
conflicts on master: src/test/isolation/isolation_schedule
pushAug 07, 06:14 -> 565b5e9d0branchdiff vs base
ResultAttPGTestsBuild / testImageWhen
success1201019 / 10192m 53s / 5m 39sdocker run ... :t253223Aug 07, 06:27
run 31153276334
executed 1019 - ccache 166 hit / 6452 miss - head 565b5e9d0 - digest sha256:237d310a94b1fe... - run 31153276334
success1201019 / 10192m 53s / 5m 13sdocker run ... @sha256:62d6674...Aug 06, 04:17
run 31070324604
executed 1019 - ccache 166 hit / 6452 miss - head 99222087e - digest sha256:62d66749b1c763... - run 31070324604
success1201019 / 10192m 47s / 5m 24sdocker run ... @sha256:db6c2dd...Aug 05, 04:17
run 30974142863
executed 1019 - ccache 166 hit / 6452 miss - head 0dbae5d1e - digest sha256:db6c2dd3543c4c... - run 30974142863
success1201019 / 10192m 52s / 5m 30sdocker run ... @sha256:d32a333...Aug 04, 04:16
run 30876610842
executed 1019 - ccache 166 hit / 6452 miss - head f12a685bb - digest sha256:d32a33373441e7... - run 30876610842
success1201018 / 10182m 54s / 5m 34sdocker run ... @sha256:2b8987e...Aug 03, 04:15
run 30783403449
executed 1018 - ccache 166 hit / 6452 miss - head d9ba30b3d - digest sha256:2b8987e6c8800e... - run 30783403449
success1201018 / 10181m 52s / 4m 15sdocker run ... @sha256:4ce9709...Aug 02, 04:12
run 30731709313
executed 1018 - ccache 166 hit / 6452 miss - head cbabe3c7d - digest sha256:4ce9709c4dde2e... - run 30731709313
success1201018 / 10182m 53s / 5m 19sdocker run ... @sha256:b753d10...Aug 01, 04:14
run 30683184730
executed 1018 - ccache 166 hit / 6452 miss - head 45f922c8e - digest sha256:b753d10d85a245... - run 30683184730
success1201017 / 10172m 15s / 4m 46sdocker run ... @sha256:737dec7...Jul 31, 04:11
run 30603093680
executed 1017 - ccache 166 hit / 6452 miss - head d4e706a3e - digest sha256:737dec76e21889... - run 30603093680
success1201017 / 10172m 55s / 5m 38sdocker run ... @sha256:a5872fc...Jul 30, 04:13
run 30512757834
executed 1017 - ccache 166 hit / 6452 miss - head c0bca8faf - digest sha256:a5872fc581b01f... - run 30512757834
success1201016 / 10162m 59s / 5m 28sdocker run ... @sha256:29143cf...Jul 29, 04:12
run 30421141150
executed 1016 - ccache 166 hit / 6452 miss - head d0f4114ec - digest sha256:29143cf4453093... - run 30421141150