Server-side base backup: why superuser, not pg_write_server_files?

back to CI dashboard

1 patchset tracked - current t45431_19

v19t45431_19posted Feb 03, 2022successwon't retryancient 5ypg 15
base8e2b6d45a Feb 02, 2022 - 1690 days / 12503 commits behind master (from history)
applyapplied Aug 18, 15:43
rebaselast tried Aug 18, 15:43 on 195e8e427
Applying: Fix non-superuser server-side basebackup test on Windows
Using index info to reconstruct a base tree...
M	src/bin/pg_basebackup/t/010_pg_basebackup.pl
Falling back to patching base and 3-way merge...
Auto-merging src/bin/pg_basebackup/t/010_pg_basebackup.pl
CONFLICT (content): Merge conflict in src/bin/pg_basebackup/t/010_pg_basebackup.pl
Patch failed at 0001 Fix non-superuser server-side basebackup test on Windows

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/bin/pg_basebackup/t/010_pg_basebackup.pl
pushAug 18, 15:43 -> e9b5db6c6branchdiff vs base
ResultAttPGTestsBuild / testImageWhen
success115625 / 6252m 06s / 3m 36sdocker run ... :t45431Aug 18, 15:53
run 32156210320
executed 625 - ccache 168 hit / 4199 miss - head e9b5db6c6 - digest sha256:0d23b388544099... - run 32156210320