Re: Server-side base backup: why superuser, not pg_write_server_files? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Server-side base backup: why superuser, not pg_write_server_files?
Date
Msg-id cd073621-5b7f-c8cb-3b09-c2c58a0fc8f3@dunslane.net
Whole thread Raw
In response to Re: Server-side base backup: why superuser, not pg_write_server_files?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Server-side base backup: why superuser, not pg_write_server_files?
List pgsql-hackers
On 2/2/22 17:52, Tom Lane wrote:
> 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.
>
>             



I've fixed this using the auth_extra method, which avoids a reload.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: should vacuum's first heap pass be read-only?
Next
From: Zhihong Yu
Date:
Subject: Re: Implementing Incremental View Maintenance