| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, 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-02 22:52:56 |
| Message-ID: | 106926.1643842376@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-02-02 23:02:39 | Re: Replace pg_controldata output fields with macros for better code manageability |
| Previous Message | Nathan Bossart | 2022-02-02 22:44:33 | Re: archive modules |