| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Marco Boeringa <marco(at)boeringa(dot)demon(dot)nl> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Potential "AIO / io workers" inter-worker locking issue in PG18? |
| Date: | 2025-10-06 14:20:22 |
| Message-ID: | jgixpsendvlphp357yxpawgr5omxj7mxs5pf3beehfccygdzzz@2exhgu3dcatm |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-10-06 14:34:49 | Re: Potential "AIO / io workers" inter-worker locking issue in PG18? |
| Previous Message | Dilip Kumar | 2025-10-06 12:04:36 | Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases |