X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EA099D1B1F8 for ; Mon, 2 Aug 2004 13:18:13 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 95406-07 for ; Mon, 2 Aug 2004 16:18:08 +0000 (GMT) Received: from mpls-qmqp-03.inet.qwest.net (mpls-qmqp-03.inet.qwest.net [63.231.195.114]) by svr1.postgresql.org (Postfix) with SMTP id DFC33D1B1E3 for ; Mon, 2 Aug 2004 13:18:07 -0300 (ADT) Received: (qmail 3946 invoked by uid 0); 2 Aug 2004 15:46:44 -0000 Received: from mpls-pop-07.inet.qwest.net (63.231.195.7) by mpls-qmqp-03.inet.qwest.net with QMQP; 2 Aug 2004 15:46:44 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-07.inet.qwest.net with SMTP; 2 Aug 2004 16:18:07 -0000 Date: Mon, 02 Aug 2004 10:19:27 -0600 Message-Id: <1091463567.27166.44.camel@localhost.localdomain> From: "Scott Marlowe" To: "Ioannis Theoharis" Cc: pgsql-performance@postgresql.org Subject: Re: Page Miss Hits In-Reply-To: References: Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200408/16 X-Sequence-Number: 7652 On Mon, 2004-08-02 at 02:11, Ioannis Theoharis wrote: > Hi, i would like to answer if there is any way in postgres to find the > page miss hits caused during a query execution. > > > Is there something like explain analyze with the page miss hits??? You're making a basic assumption that is (at least currently) untrue, and that is that PostgreSQL has it's own cache. It doesn't. It has a buffer that drops buffer back into the free pool when the last referencing backend concludes and shuts down. So, PostgreSQL currently relies on the kernel to cache for it. So, what you need is a tool that monitors the kernel cache usage and its hit rate. I'm not familiar with any, but I'm sure something out there likely does that.