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 4EA4C3A2BB9 for ; Fri, 5 Nov 2004 02:53:59 +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 17518-10 for ; Fri, 5 Nov 2004 02:53:54 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id DB7A43A2BCF for ; Fri, 5 Nov 2004 02:53:57 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id iA52rmJD020570 for ; Fri, 5 Nov 2004 02:53:54 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id iA52o0wa019712 for pgsql-performance@postgresql.org; Fri, 5 Nov 2004 02:50:00 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Anything to be gained from a 'Postgres Filesystem'? Date: Thu, 04 Nov 2004 21:05:36 -0500 Organization: cbbrowne Computing Inc Lines: 30 Message-ID: References: <20041104120047.62810c8f@kingfisher.intern.logi-track.com> <60bred39bg.fsf@dba2.int.libertyrms.com> <1099595027.4320.663.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:6uXmyIDDY5ACBmluA/ABI0QWUAg= To: pgsql-performance@postgresql.org 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/81 X-Sequence-Number: 9035 After a long battle with technology, simon@2ndquadrant.com (Simon Riggs), an earthling, wrote: > On Thu, 2004-11-04 at 15:47, Chris Browne wrote: > >> Another thing that would be valuable would be to have some way to say: >> >> "Read this data; don't bother throwing other data out of the cache >> to stuff this in." >> >> 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. > > Seq scans do get put in cache, but in a way that means they don't > spoil the main bulk of the cache. We're not talking about the same cache. ARC does these exact things for _shared memory_ cache, and is the obvious inspiration. But it does more or less nothing about the way OS file buffer cache is managed, and the handling of _that_ would be the point of modifying OS filesystem semantics. -- select 'cbbrowne' || '@' || 'linuxfinances.info'; http://www3.sympatico.ca/cbbrowne/oses.html Have you ever considered beating yourself with a cluestick?