Add “FOR UPDATE NOWAIT” lock details to the log.

back to CI dashboard

1 patchset tracked - current t50271_41

v41t50271_41posted Jun 13, 09:59successwon't retrystale 3mopg 19
base3692a622d Jun 11, 16:29 - 100 days / 970 commits behind master (from history)
applyapplied Aug 18, 13:39
rebaselast tried Aug 18, 13:39 on 033f39e69
Applying: Make log_lock_failures support LOCK NOWAIT
Using index info to reconstruct a base tree...
M	doc/src/sgml/config.sgml
M	src/backend/catalog/namespace.c
M	src/backend/commands/lockcmds.c
M	src/backend/commands/repack.c
M	src/backend/commands/tablecmds.c
M	src/backend/commands/vacuum.c
M	src/backend/postmaster/autovacuum.c
Falling back to patching base and 3-way merge...
Auto-merging src/backend/postmaster/autovacuum.c
Auto-merging src/backend/commands/vacuum.c
Auto-merging src/backend/commands/tablecmds.c
Auto-merging src/backend/commands/repack.c
CONFLICT (content): Merge conflict in src/backend/commands/repack.c
Auto-merging src/backend/commands/lockcmds.c
Auto-merging src/backend/catalog/namespace.c
Auto-merging doc/src/sgml/config.sgml
Patch failed at 0001 Make log_lock_failures support LOCK NOWAIT

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/repack.c
pushAug 18, 13:39 -> 2d535998bbranchdiff vs base
ResultAttPGTestsBuild / testImageWhen
success1191005 / 10051m 53s / 4m 11sdocker run ... :t50271Aug 18, 13:51
run 32143661532
executed 1005 - ccache 145 hit / 6474 miss - head 2d535998b - digest sha256:ec9ec475187ad0... - run 32143661532