| 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 17:40:41 |
| Message-ID: | 3894060.1646415641@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:
> On 2022-03-04 12:23:43 -0500, Tom Lane wrote:
>> pg_regress thinks the postmaster is listening to a Unix socket.
> pg_regress outputs the above message when neither PGHOST, PGPORT or
> --host/--port are set. On windows that nevertheless ends up with connecting to
> localhost.
Yeah, I just traced that down. pg_regress was not updated when libpq's
behavior was changed for platform-varying DEFAULT_PGSOCKET_DIR.
I'll go fix that, but you're right that it's cosmetic.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-03-04 17:46:44 | Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b |
| Previous Message | Andres Freund | 2022-03-04 17:37:51 | Re: Regression tests failures on Windows Server 2019 - on master at commit # d816f366b |