| From: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Server-side base backup: why superuser, not pg_write_server_files? |
| Date: | 2022-02-03 16:20:11 |
| Message-ID: | 87iltvzzus.fsf@wibble.ilmari.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> I wrote:
>> The Windows animals don't like this:
>> pg_basebackup: error: connection to server at "127.0.0.1", port 59539
>> failed: FATAL: SSPI authentication failed for user "backupuser"
>
>> Not sure whether we have a standard method to get around that.
>
> Ah, right, we do. Looks like adding something like
>
> auth_extra => [ '--create-role', 'backupuser' ]
>
> to the $node->init call would do it, or you could mess with
> invoking pg_regress --config-auth directly.
This was enough incentive for me to set up Cirrus-CI for my fork on
GitHub, and the auth_extra approach in the attached patch fixed the
test:
https://cirrus-ci.com/task/6578617030279168?logs=test_bin#L21
- ilmari
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-non-superuser-server-side-basebackup-test-on-Win.patch | text/x-diff | 1017 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yugo NAGATA | 2022-02-03 16:25:48 | Re: Implementing Incremental View Maintenance |
| Previous Message | John Naylor | 2022-02-03 16:18:43 | Re: do only critical work during single-user vacuum? |