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.94.2) (envelope-from ) id 1tSInq-00FXYJ-WC for pgsql-hackers@arkaria.postgresql.org; Mon, 30 Dec 2024 16:39:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tSInp-00D4Ug-VU for pgsql-hackers@arkaria.postgresql.org; Mon, 30 Dec 2024 16:39:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tSInp-00D4UY-MT for pgsql-hackers@lists.postgresql.org; Mon, 30 Dec 2024 16:39:37 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tSIni-002N32-Vh for pgsql-hackers@postgresql.org; Mon, 30 Dec 2024 16:39:36 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 4BUGdOH63861404; Mon, 30 Dec 2024 11:39:24 -0500 From: Tom Lane To: Bruce Momjian cc: Jelte Fennema-Nio , torikoshia , Pgsql Hackers Subject: Re: RFC: Allow EXPLAIN to Output Page Fault Information In-reply-to: References: <1614321.1735055528@sss.pgh.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 30 Dec 2024 11:19:47 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3861402.1735576764.1@sss.pgh.pa.us> Date: Mon, 30 Dec 2024 11:39:24 -0500 Message-ID: <3861403.1735576764@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Bruce Momjian writes: > On Fri, Dec 27, 2024 at 03:15:40PM +0100, Jelte Fennema-Nio wrote: >> On Tue Dec 24, 2024 at 4:52 PM CET, Tom Lane wrote: >>> torikoshia writes: >>>> I have attached a PoC patch that modifies EXPLAIN to include page >>>> fault information during both the planning and execution phases of a >>>> query. > I certainly would love to see storage I/O numbers as distinct from > kernel read I/O numbers. Me too, but I think it is 100% wishful thinking to imagine that page fault counts match up with that. Maybe there are filesystems where a read that we request maps one-to-one with a subsequent page fault, but it hardly seems likely to me that that's universal. Also, you can't tell page faults for reading program code apart from those for data, and you won't get any information at all about writes. regards, tom lane