pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)

back to CI dashboard

1 patchset tracked - current t41836_171

v171t41836_171posted Apr 10, 2023successwon't retryancient 3ypg 16
base3d03b24c3 Apr 08, 2023 - 1260 days / 9432 commits behind master (from history)
applyapplied Aug 18, 15:15
rebaselast tried Aug 18, 15:15 on 195e8e427
Applying: Document standalone backend type in pg_stat_activity
Using index info to reconstruct a base tree...
M	doc/src/sgml/monitoring.sgml
Falling back to patching base and 3-way merge...
Auto-merging doc/src/sgml/monitoring.sgml
CONFLICT (content): Merge conflict in doc/src/sgml/monitoring.sgml
Patch failed at 0001 Document standalone backend type in pg_stat_activity

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: doc/src/sgml/monitoring.sgml
pushAug 18, 15:16 -> 99346701fbranchdiff vs base
ResultAttPGTestsBuild / testImageWhen
success116773 / 7732m 58s / 4m 09sdocker run ... :t41836Aug 18, 15:25
run 32153413494
executed 773 - ccache 212 hit / 4360 miss - head 99346701f - digest sha256:d025aec7bb201b... - run 32153413494