Re: Potential "AIO / io workers" inter-worker locking issue in PG18? - Mailing list pgsql-bugs

From Marco Boeringa
Subject Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
Date
Msg-id a031c5bc-e61e-4ef7-a52c-d6759c97f265@boeringa.demon.nl
Whole thread Raw
In response to Potential "AIO / io workers" inter-worker locking issue in PG18?  (Marco Boeringa <marco@boeringa.demon.nl>)
Responses Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
List pgsql-bugs
Just found out about the other thread, which seems to describe an issue 
that may well be related to the problems I observe in my multi-threaded 
Python implementation using PostgreSQL 18:


https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BHh7u3YpPLKQS%2BB7KJu0Bw99EjhuPuvBRVccDfgod95g%40mail.gmail.com#969d704180758e8dbd124604206175e0

As I have zero experience compiling PostgreSQL from scratch and 
PostgreSQL development in general, I will unfortunately avoid going down 
the rabbit hole of such an attempt to be able to test the patch, but 
will eagerly await PG18.1 which hopefully will have it included and 
might fix the issues I observed.

Marco




pgsql-bugs by date:

Previous
From: Zane Duffield
Date:
Subject: Re: Date/Time parsing of ISO 8601 timestamps with commas
Next
From: Andres Freund
Date:
Subject: Re: Potential "AIO / io workers" inter-worker locking issue in PG18?