Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vg4dh-007vXO-0O for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Jan 2026 17:26:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vg4dg-00BjSO-0a for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Jan 2026 17:26:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vg4df-00BjSE-2U for pgsql-hackers@lists.postgresql.org; Wed, 14 Jan 2026 17:26:36 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vg4dc-000QEz-0B for pgsql-hackers@lists.postgresql.org; Wed, 14 Jan 2026 17:26:34 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id E1886511520 for ; Wed, 14 Jan 2026 18:26:28 +0100 (CET) Received: from s899.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id C8B35510759; Wed, 14 Jan 2026 18:26:28 +0100 (CET) Received: from s473.loopia.se (unknown [172.22.191.6]) by s899.loopia.se (Postfix) with ESMTP id C64772C8B90D; Wed, 14 Jan 2026 18:26:28 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s473.loopia.se (amavisd-new); dkim=pass (2048-bit key) header.d=proxel.se Received: from s899.loopia.se ([172.22.191.5]) by s473.loopia.se (s473.loopia.se [172.22.190.13]) (amavisd-new, port 10024) with LMTP id rSwKKWHpuCGT; Wed, 14 Jan 2026 18:26:28 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: andreas@proxel.se X-Loopia-Originating-IP: 147.28.75.140 Received: from [192.168.0.121] (customer-147-28-75-140.stosn.net [147.28.75.140]) (Authenticated sender: andreas@proxel.se) by s899.loopia.se (Postfix) with ESMTPSA id 3DF622C8B978; Wed, 14 Jan 2026 18:26:28 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proxel.se; s=loopiadkim1707418970; t=1768411588; bh=GXzS7yJFgpt0IM7Kd0YAapR0h3g+GNiyNABSuyeX6e8=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=aMJY2rcAS3wDD50+rBuecCFt9v59bE//5Gcjn6tm+b4SKdQSFs4t23AZveeZtXgp1 ZMrKk7QA6NMN/zN2LO2VYota4KZvo5Vv52+W0zrGSUv/9MYKPFGzwHXVd9LmPuwmC1 gLvAvrTqoqbRJV4NvU8ZLcR7xLOvp8oXERkQpoKaXxSZqSzvUPOYVE9xy0UEAOo0sV LAgVsN4K/22votUbo+yJ+tOYXmeg47zjt8N5Z3dV6BFwaG2ddA2Vvg2e9zamZDXtj0 VrqG3xJUIKpjtEDbAuzKE/snxcS8SdJPbtMS1d1Pl3lGSlyt/rkSLrClmO6tj42/rL CX6YEzkY+gJDg== Message-ID: <10a90d37-3471-4ea4-a492-117c7997d4ed@proxel.se> Date: Wed, 14 Jan 2026 18:26:27 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] check kernel version for io_method To: Jakub Wartak , Steven Niu Cc: Pierre , "pgsql-hackers@lists.postgresql.org" References: <17879f12-609b-4730-bfff-6dd11a46d5e6@gmail.com> <98b4032e-64b9-4d36-bc65-2dc4d0d80a58@proxel.se> From: Andreas Karlsson Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/14/26 12:14 PM, Jakub Wartak wrote: > I haven't looked at this patch, however the above statement is not > completely true. There is a parallel problem [1] related to kernel > version, where if you do not run proper kernel version (>= 6.5) or > proper liburing version, then fork() (-> all connections established) > are going to be slow slugging under more than basic load due to lack > of "combined memory mapping creation" (so technically speaking > recommending someone to go to 5.6.x but < 6.5 IMHO is also not good > advice). See first message in that [1] for a performance report about > this. IMHVO if we are checking for kernel versions we could also warn > about performance regression (something like merge those two patches > if one wants to have a good io_uring experience). We can probe for that too, which we already do. If you call pgaio_uring_ring_shmem_size() it will return 0 on Linux <6.5. Which I think eve further supports probing for the features we need rather than looking at the kernel version. Andreas