logical replication: restart_lsn can go backwards (and more), seems broken since 9.4

back to CI dashboard

1 patchset tracked - current t50521_42

v42t50521_42posted Nov 19, 2024successwon't retryancient 2ypg 18
basee5ed873b1 Nov 16, 2024 - 673 days / 5566 commits behind master (from history)
applyapplied Aug 18, 14:39
rebaselast tried Aug 18, 14:39 on 195e8e427
Applying: asserts: restart_lsn
Using index info to reconstruct a base tree...
M	src/backend/replication/logical/logical.c
M	src/backend/replication/slot.c
Falling back to patching base and 3-way merge...
Auto-merging src/backend/replication/slot.c
CONFLICT (content): Merge conflict in src/backend/replication/slot.c
Auto-merging src/backend/replication/logical/logical.c
Patch failed at 0001 asserts: restart_lsn

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/backend/replication/slot.c
pushAug 18, 14:39 -> 1dbb6149dbranchdiff vs base
ResultAttPGTestsBuild / testImageWhen
success118855 / 8552m 33s / 3m 32sdocker run ... :t50521Aug 18, 14:53
run 32149708970
executed 855 - ccache 82 hit / 6421 miss - head 1dbb6149d - digest sha256:f2ab72465a05eb... - run 32149708970