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

From Andres Freund
Subject Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
Date
Msg-id jgixpsendvlphp357yxpawgr5omxj7mxs5pf3beehfccygdzzz@2exhgu3dcatm
Whole thread Raw
In response to Re: Potential "AIO / io workers" inter-worker locking issue in PG18?  (Marco Boeringa <marco@boeringa.demon.nl>)
List pgsql-bugs
Hi,

On 2025-10-05 22:22:32 +0200, Marco Boeringa wrote:
> I realized that my observation of the pg_aios view being empty was likely
> with the "io_method = sync" option set, which I guess doesn't use or fill
> the pg_aios view? Can you confirm the pg_aios view is unused with "io_method
> = sync", this aspect is not documented in the PostgreSQL help? Anyway, I
> will need to re-test with 'worker' set.

pg_aios is populated even with io_method = sync, albeit with at most one entry
entry per backend.

If there were no entries in pg_aios at the time of your hang, it doesn't seem
likely - although not impossible - for AIO to be responsible.

Greetings,

Andres Freund



pgsql-bugs by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
Next
From: Andres Freund
Date:
Subject: Re: Potential "AIO / io workers" inter-worker locking issue in PG18?