Re: Server-side base backup: why superuser, not pg_write_server_files?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
Cc: Robert Haas <robertmhaas@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-02-02T22:43:31Z
Lists: pgsql-hackers
=?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= <ilmari@ilmari.org> writes: > Here's a follow-on patch that adds a test for non-superuser server-side > basebackup, which crashes without your patch and passes with it. The Windows animals don't like this: # Running: pg_basebackup --no-sync -cfast -U backupuser --target server:C:\\prog\\bf\\root\\HEAD\\pgsql.build\\src\\bin\\pg_basebackup\\tmp_check\\tmp_test_VGMM/backuponserver -X none pg_basebackup: error: connection to server at "127.0.0.1", port 59539 failed: FATAL: SSPI authentication failed for user "backupuser" not ok 108 - backup target server # Failed test 'backup target server' # at t/010_pg_basebackup.pl line 527. Not sure whether we have a standard method to get around that. regards, tom lane
Commits
-
Fix server crash bug in 'server' backup target.
- 8e2b6d45a033 15.0 landed
-
Adjust server-side backup to depend on pg_write_server_files.
- 7f6772317b4a 15.0 landed