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-29 11:24:51
Message-ID: 20230729112451.GA1031795@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 28, 2023 at 04:00:00PM +0300, Alexander Lakhin wrote:
> 28.07.2023 14:42, Noah Misch wrpte:
> >That was about a bug that appears when using TCP sockets. ...
>
> Yes, and according to the failed test output, TCP sockets were used:
>
> #                   'pg_amcheck: error: connection to server at
> "127.0.0.1", port 49393 failed: server closed the connection
> unexpectedly
> #       This probably means the server terminated abnormally
> #       before or while processing the request.

I think we were talking about different details. Agreed, bug #16678 probably
did cause the failure in the original post. I was saying that bug has no
connection to the "scary comment", though.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2023-07-29 12:23:29 Re: logical decoding and replication of sequences, take 2
Previous Message Bharath Rupireddy 2023-07-29 06:47:40 Re: add timing information to pg_upgrade