| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b |
| Date: | 2022-03-04 21:51:32 |
| Message-ID: | 3983061.1646430692@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)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??)
> The dblink and fdw failures can presumably be fixed by passing current_user as
> the username. That seems like a good idea anyway?
I don't think it's a good idea to hack that without understanding
why it's suddenly going wrong.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-03-04 21:56:57 | Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b |
| Previous Message | Andres Freund | 2022-03-04 21:42:06 | Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b |