Re: Postgres v15 windows bincheck regression test failures

From: Noah Misch <noah(at)leadboat(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Russell Foster <russell(dot)foster(dot)coding(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Postgres v15 windows bincheck regression test failures
Date: 2023-07-28 11:42:14
Message-ID: 20230728114214.GA1004522@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 28, 2023 at 07:00:01AM +0300, Alexander Lakhin wrote:
> 28.07.2023 05:17, Noah Misch wrote:
> >On Tue, Jun 20, 2023 at 07:49:52AM -0400, Russell Foster wrote:
> >>/*
> >>* We don't use Unix-domain sockets on Windows by default, even if the
> >>* build supports them. (See comment at remove_temp() for a reason.)
> >>* Override at your own risk.
> >>*/
> >>
> >>Is there some sort of race condition in the SSPI code that sometimes
> >>doesn't gracefully finish/close the connection when the backend
> >>decides to exit due to error?
> >No. remove_temp() is part of test driver "pg_regress". Non-test usage is
> >unaffected. Even for test usage, folks have reported no failures from the
> >cause mentioned in the remove_temp() comment.
>
> It seems to me that it's just another manifestation of bug #16678 ([1]).
> See also commits 6051857fc and 29992a6a5.
>
> [1] https://www.postgresql.org/message-id/flat/16678-253e48d34dc0c376%40postgresql.org

That was about a bug that appears when using TCP sockets. The remove_temp()
comment involves code that doesn't run when using TCP sockets. I don't think
they can be manifestations of the same phenomenon.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Anthonin Bonnefoy 2023-07-28 11:45:24 Re: POC: Extension for adding distributed tracing - pg_tracing
Previous Message Bharath Rupireddy 2023-07-28 11:27:18 Re: WAL Insertion Lock Improvements