Request a Demo
Home   >   mailing lists

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 ut77uhgxfttgf44uc5rgxpsewbxxydraw76m4okry4hk4ek7t5@kewogxyo6ezn
Whole thread Raw
In response to Re: Potential "AIO / io workers" inter-worker locking issue in PG18?  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
Tree view 
Hi,

On 2025-10-07 19:03:40 -0400, Andres Freund wrote:
> On 2025-10-08 00:13:34 +0200, Marco Boeringa wrote:
> So somehow >60% of the CPU time is spent fetching tuples corresponding to
> index entries. That seems ... a lot.  Is it possible that you have a lot of
> dead rows in the involved tables?
> 
> I don't immediately see how this could be related to AIO.

Can you share the query and explain for it that was running in the "stuck"
backend?

Greetings,

Andres Freund

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
Next
From: Michael Paquier
Date:
Subject: Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c