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 46EBE3A4985 for ; Thu, 4 Nov 2004 20:43:18 +0000 (GMT) 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 13182-10 for ; Thu, 4 Nov 2004 20:43:15 +0000 (GMT) Received: from cmailg1.svr.pol.co.uk (cmailg1.svr.pol.co.uk [195.92.195.171]) by svr1.postgresql.org (Postfix) with ESMTP id E694F3A4980 for ; Thu, 4 Nov 2004 20:43:16 +0000 (GMT) Received: from modem-462.lion.dialup.pol.co.uk ([217.135.161.206] helo=[192.168.0.102]) by cmailg1.svr.pol.co.uk with esmtp (Exim 4.14) id 1CPoRs-0002UZ-MR; Thu, 04 Nov 2004 20:43:12 +0000 Subject: Re: Anything to be gained from a 'Postgres Filesystem'? From: Simon Riggs To: Tom Lane Cc: Chris Browne , pgsql-performance@postgresql.org In-Reply-To: <28208.1099596848@sss.pgh.pa.us> References: <20041104120047.62810c8f@kingfisher.intern.logi-track.com> <60bred39bg.fsf@dba2.int.libertyrms.com> <1099595027.4320.663.camel@localhost.localdomain> <28208.1099596848@sss.pgh.pa.us> Content-Type: text/plain Organization: 2nd Quadrant Message-Id: <1099600845.5682.3.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 04 Nov 2004 20:40:45 +0000 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: 200411/58 X-Sequence-Number: 9012 On Thu, 2004-11-04 at 19:34, Tom Lane wrote: > Simon Riggs writes: > > On Thu, 2004-11-04 at 15:47, Chris Browne wrote: > >> Something like a "read_uncached()" call... > >> > >> That would mean that a seq scan or a vacuum wouldn't force useful data > >> out of cache. > > > ARC does almost exactly those two things in 8.0. > > But only for Postgres' own shared buffers. The kernel cache still gets > trashed, because we have no way to suggest to the kernel that it not > hang onto the data read in. I guess a difference in viewpoints. I'm inclined to give most of the RAM to PostgreSQL, since as you point out, the kernel is out of our control. That way, we can do what we like with it - keep it or not, as we choose. -- Best Regards, Simon Riggs