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 1tQ7Cj-000BoF-Jm for pgsql-hackers@arkaria.postgresql.org; Tue, 24 Dec 2024 15:52:17 +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 1tQ7Ci-006M1w-By for pgsql-hackers@arkaria.postgresql.org; Tue, 24 Dec 2024 15:52:16 +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 1tQ7Ci-006M1o-2b for pgsql-hackers@lists.postgresql.org; Tue, 24 Dec 2024 15:52:15 +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 1tQ7Cf-001PPQ-7s for pgsql-hackers@postgresql.org; Tue, 24 Dec 2024 15:52:15 +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 4BOFq8OF1614322; Tue, 24 Dec 2024 10:52:09 -0500 From: Tom Lane To: torikoshia cc: Pgsql Hackers Subject: Re: RFC: Allow EXPLAIN to Output Page Fault Information In-reply-to: References: Comments: In-reply-to torikoshia message dated "Tue, 24 Dec 2024 17:53:06 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1614320.1735055528.1@sss.pgh.pa.us> Date: Tue, 24 Dec 2024 10:52:08 -0500 Message-ID: <1614321.1735055528@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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. Surely these numbers would be too unstable to be worth anything. regards, tom lane