From: Marco Boeringa <marco@boeringa.demon.nl>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-bugs@lists.postgresql.org, Thom Brown <thom@linux.com>
Subject: Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
Date: Fri, 10 Oct 2025 23:26:38 +0200
Message-ID: <a031c5bc-e61e-4ef7-a52c-d6759c97f265@boeringa.demon.nl> (raw)
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...
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: marco@boeringa.demon.nl, andres@anarazel.de, thom@linux.com
Subject: Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
In-Reply-To: <a031c5bc-e61e-4ef7-a52c-d6759c97f265@boeringa.demon.nl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox