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

From Marco Boeringa
Subject Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
Date
Msg-id 249a5c55-5e05-4d69-bfd3-0ba972a79530@boeringa.demon.nl
Whole thread Raw
In response to Re: Potential "AIO / io workers" inter-worker locking issue in PG18?  (Andres Freund <andres@anarazel.de>)
Responses Re: Potential "AIO / io workers" inter-worker locking issue in PG18?
List pgsql-bugs
It didn't work: as soon as I attempted to run perf, it emitted the 
warning message about the kernel version mismatch with suggestions of 
package to install.

However, I now realized after further digging, that Ubuntu usually has 
multiple kernel versions installed. I have now attempted to add the GRUB 
boot menu, which should allow me to boot with the older 6.8 version of 
the kernel (which was available during configuration of GRUB), and 
hopefully run perf with that version of the kernel.

Marco

Op 6-10-2025 om 23:39 schreef Andres Freund:
> On 2025-10-06 22:41:31 +0200, Marco Boeringa wrote:
>> Hi Andres,
>>
>> I now found out that I do have a 'perf' living under one of 'usr' folders,
>> but unfortunately, this is the 6.8 kernel version:
>>
>> /usr/lib/linux-tools-6.8.0-85
>>
>> None of the other suggested packages and their likely install folders seem
>> to contain perf.
>>
>> Since perf appears and rather understandably seems to need to exactly match
>> the kernel version, I can't use this one, as my kernel was already upgraded
>> to 6.14 by a more or less forced update in Software Updater.
> I'm pretty sure that you can use any halfway-recent perf binary, they don't
> actually need to match exactly. I don't know why ubuntu insists on a perfect
> match. I regularly run completely different versions.
>
> Greetings,
>
> Andres Freund



pgsql-bugs by date:

Previous
From: Sajith Prabhakar Shetty
Date:
Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Next
From: Marco Boeringa
Date:
Subject: Re: Potential "AIO / io workers" inter-worker locking issue in PG18?