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 F1AC6D1B181 for ; Mon, 2 Aug 2004 17:50:59 -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 12601-05 for ; Mon, 2 Aug 2004 20:50:56 +0000 (GMT) Received: from pns.mm.eutelsat.org (pns.mm.eutelsat.org [194.214.173.227]) by svr1.postgresql.org (Postfix) with ESMTP id AE1A0D1B171 for ; Mon, 2 Aug 2004 17:50:52 -0300 (ADT) Received: from nts-03.mm.eutelsat.org (localhost [127.0.0.1]) by pns.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id i72KoXd25533; Mon, 2 Aug 2004 22:50:34 +0200 Received: from [127.0.0.1] (accesspoint.mm.eutelsat.org [194.214.173.4]) by nts-03.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id i72KoqZ19759; Mon, 2 Aug 2004 22:50:52 +0200 Message-ID: <410EA90C.7030707@bigfoot.com> Date: Mon, 02 Aug 2004 22:50:20 +0200 From: Gaetano Mendola User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Marlowe Cc: "pgsql-performance@postgresql.org" Subject: Re: Page Miss Hits References: <1091463567.27166.44.camel@localhost.localdomain> <410E6F34.6040300@bigfoot.com> <1091468476.27166.48.camel@localhost.localdomain> In-Reply-To: <1091468476.27166.48.camel@localhost.localdomain> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/18 X-Sequence-Number: 7654 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Scott Marlowe wrote: | On Mon, 2004-08-02 at 10:43, Gaetano Mendola wrote: | |>Scott Marlowe wrote: |> |>>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. |> |>Are you sure of this ? What is the meaning of the ARC recently introduced |>then ? | | | Yes I am. Test it yourself, setup a couple of backends, select * from | some big tables, then, one at a time, shut down the psql clients and | when the last one closes, the shared mem goes away. Run another client, | do select * from the big table, and watch the client size grow from a | few meg to a size large enough to hold the whole table (or however much | your shared_buffers will hold.) | | While someone may make ARC and the shared buffers act like a cache some | day (can't be that hard, most of the work is done really) right now it's | not how it works. | | ARC still helps, since it makes sure the shared_buffers don't all get | flushed from the useful small datasets when a seq scan gets executed. I'm still not convinced. Why the last backend alive, have to throw away bunch of memory copied in the SHM? And again, the ARC is a replacement policy for a cache, which one ? Regards Gaetano Mendola -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBDqkL7UpzwH2SGd4RAsQFAKCWVpCXKgRfE1nc44ZmtEaIrtNaIQCgr4fd Hx2NiuRzV0UQ3Na9g/zQbzE= =XWua -----END PGP SIGNATURE-----