Re: Cleaning up threading code - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Cleaning up threading code
Date
Msg-id CA+hUKGKLi4FM6aex8gjYxCU=uAJrzmVhB=EPagskvLP8gWjAhA@mail.gmail.com
Whole thread Raw
In response to Re: Cleaning up threading code  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Wed, Jul 12, 2023 at 3:34 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> On Wed, Jul 12, 2023 at 3:21 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> > Apparently "drongo" didn't like something about this commit, and an
> > ecpg test failed, but I can't immediately see why.  Just "server
> > closed the connection unexpectedly".  drongo is running the new Meson
> > buildfarm variant on Windows+MSVC, so, being still in development, I
> > wonder if some diagnostic clue/log/backtrace etc is not being uploaded
> > yet.  FWIW Meson+Windows+MSVC passes on CI.
>
> Oh, that's probably unrelated to this commit.  It's failed 6 times
> like that in the past ~3 months.

Ah, right, that is a symptom of the old Windows TCP linger vs process
exit thing.  Something on my list to try to investigate again, but not
today.

https://www.postgresql.org/message-id/flat/16678-253e48d34dc0c376%40postgresql.org



pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL
Next
From: Michael Paquier
Date:
Subject: Re: 'ERROR: attempted to update invisible tuple' from 'ALTER INDEX ... ATTACH PARTITION' on parent index