Message-ID: <a031c5bc-e61e-4ef7-a52c-d6759c97f265@boeringa.demon.nl>
Date: Fri, 10 Oct 2025 23:26:38 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-bugs@lists.postgresql.org, Thom Brown <thom@linux.com>
From: Marco Boeringa <marco@boeringa.demon.nl>
Subject: Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/a031c5bc-e61e-4ef7-a52c-d6759c97f265%40boeringa.demon.nl>
Precedence: bulk

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