Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b
Date
Msg-id cf1190f9-53ff-7367-13d7-52b3464b0348@dunslane.net
Whole thread Raw
In response to Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 3/4/22 17:04, Andres Freund wrote:
> Hi,
>
> On 2022-03-04 16:51:32 -0500, Tom Lane wrote:
>> Andres Freund <andres@anarazel.de> writes:
>>> That fixed the immediate problem, but dblink, postgres_fdw tests failed:
>>> +ERROR:  could not establish connection
>>> +DETAIL:  connection to server at "localhost" (::1), port 5432 failed: FATAL:
>>>  role "SYSTEM" does not exist
>> [ scratches head... ]  Where is libpq getting that username from?
>> Why is it different from whatever we'd determined during initdb?
>> (Maybe a case-folding issue??)
> When running as a service (via pg_ctl register) the default username to run
> under appears to be SYSTEM. Which then differs from the user that vcregress.pl
> runs under. Trying to make it use the current user now - I don't know what
> permissions services are needed to run a service as a user or such.


SeServiceLogonRight is what the user needs to run the service.


To manage it (e.g. stop or start it) they need some extra permissions,
see for example <http://get-carbon.org/Grant-ServicePermission.html>


cheers


andrew



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




pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Make unlogged table resets detectable
Next
From: Andrew Dunstan
Date:
Subject: Re: [PoC] Let libpq reject unexpected authentication requests