RE: Recovery at replica stuck because recovery incorrectly trusts an old high-water mark

back to CI dashboard

1 patchset tracked - current t253928_1

v1t253928_1posted Sep 24, 18:30successneeds rebaserecent 29dpg 20
base92a734bf5 Oct 05, 23:16 on master
applyapplied Oct 05, 23:49
rebaselast tried about 16 hours ago on e5f6a7a28
Applying: Keep flushedUpto monotonic; reset applyFlushedUpto after a failed read.
Using index info to reconstruct a base tree...
M	src/backend/access/transam/xlogrecovery.c
M	src/backend/replication/walreceiver.c
M	src/test/recovery/meson.build
Falling back to patching base and 3-way merge...
Auto-merging src/test/recovery/meson.build
CONFLICT (content): Merge conflict in src/test/recovery/meson.build
Auto-merging src/backend/replication/walreceiver.c
Auto-merging src/backend/access/transam/xlogrecovery.c
Patch failed at 0001 Keep flushedUpto monotonic; reset applyFlushedUpto after a failed read.

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/recovery/meson.build
pushOct 05, 23:49 -> 4df3feeb6branchdiff vs base
ResultAttPGTestsBuild / testImageWhen
success1201040 / 10402m 48s / 5m 31sdocker run ... :t253928Oct 06, 00:00
run 37390719895
executed 1040 - ccache 78 hit / 6544 miss - head 4df3feeb6 - digest sha256:7b51f5136c7a85... - run 37390719895
success1201040 / 10402m 57s / 5m 24sdocker run ... @sha256:ecd80b4...Oct 04, 23:56
run 37244941976
executed 1040 - ccache 78 hit / 6544 miss - head d15e10199 - digest sha256:ecd80b4a669cc9... - run 37244941976
success1201040 / 10402m 52s / 5m 34sdocker run ... @sha256:000db43...Oct 03, 23:56
run 37162779463
executed 1040 - ccache 78 hit / 6544 miss - head d8a24aaae - digest sha256:000db431089c3c... - run 37162779463
success1201040 / 10402m 54s / 5m 30sdocker run ... @sha256:82a2736...Oct 02, 23:55
run 37079037261
executed 1040 - ccache 78 hit / 6544 miss - head b8c091e1f - digest sha256:82a2736ea7ab9d... - run 37079037261
success1201040 / 10402m 14s / 4m 31sdocker run ... @sha256:58de85e...Oct 01, 23:52
run 36942283781
executed 1040 - ccache 78 hit / 6544 miss - head 31856782d - digest sha256:58de85e413cc93... - run 36942283781
success1201040 / 10402m 53s / 5m 31sdocker run ... @sha256:1aa82a7...Sep 30, 23:51
run 36792321103
executed 1040 - ccache 78 hit / 6544 miss - head 85c707152 - digest sha256:1aa82a709ca703... - run 36792321103
success1201040 / 10402m 12s / 4m 43sdocker run ... @sha256:cd7f63b...Sep 29, 23:46
run 36646113677
executed 1040 - ccache 78 hit / 6544 miss - head 2e8cef802 - digest sha256:cd7f63b6f1f5a1... - run 36646113677
success1201040 / 10401m 51s / 3m 54sdocker run ... @sha256:ac7f36a...Sep 28, 23:42
run 36498671230
executed 1040 - ccache 78 hit / 6544 miss - head 8e001f3da - digest sha256:ac7f36a923a41d... - run 36498671230
success1201040 / 10402m 10s / 4m 30sdocker run ... @sha256:332bc98...Sep 27, 23:41
run 36359017641
executed 1040 - ccache 78 hit / 6544 miss - head 9d44a12dc - digest sha256:332bc982337e25... - run 36359017641
success1201040 / 10402m 53s / 5m 30sdocker run ... @sha256:226fbf6...Sep 26, 19:01
run 36263912261
executed 1040 - ccache 78 hit / 6544 miss - head 5fa94b8f6 - digest sha256:226fbf65c3acee... - run 36263912261
success1201040 / 10402m 47s / 5m 23sdocker run ... @sha256:252faf3...Sep 25, 18:46
run 36174475710
executed 1040 - ccache 78 hit / 6544 miss - head b1a4f3c9c - digest sha256:252faf345bd030... - run 36174475710
success1201039 / 10391m 49s / 4m 15sdocker run ... @sha256:a4d622d...Sep 24, 18:41
run 36042080207
executed 1039 - ccache 78 hit / 6544 miss - head d5662aca5 - digest sha256:a4d622d7713e8b... - run 36042080207