BUG #19360: Bug Report: Logical Replication initial sync fails with "conflict=update_origin_differs" PG12 toPG18

back to CI dashboard

1 patchset tracked - current t73430_11

v11t73430_11posted Jun 04, 11:37successwon't retrystale 4mopg 19
basebf7d19be9 May 17, 01:01 - 127 days / 1126 commits behind master (from history)
applyapplied Jul 28, 14:42
rebaselast tried Jul 28, 14:42 on 8a045f760
Applying: Avoid spurious update_origin_differs conflicts
Using index info to reconstruct a base tree...
M	src/backend/catalog/pg_subscription.c
M	src/backend/commands/subscriptioncmds.c
M	src/backend/replication/logical/sequencesync.c
M	src/backend/replication/logical/worker.c
Falling back to patching base and 3-way merge...
Auto-merging src/backend/replication/logical/worker.c
Auto-merging src/backend/replication/logical/sequencesync.c
Auto-merging src/backend/commands/subscriptioncmds.c
CONFLICT (content): Merge conflict in src/backend/commands/subscriptioncmds.c
Auto-merging src/backend/catalog/pg_subscription.c
Patch failed at 0001 Avoid spurious update_origin_differs conflicts

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/commands/subscriptioncmds.c
pushJul 28, 14:42 -> f103aa28cbranchdiff vs base
ResultAttPGTestsBuild / testImageWhen
success1191003 / 10032m 50s / 5m 06sdocker run ... :t73430Jul 28, 14:53
run 30369678408
executed 1003 - ccache 145 hit / 6474 miss - head f103aa28c - digest sha256:9db01fc4992149... - run 30369678408