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 F3C633A48D3 for ; Thu, 4 Nov 2004 16:23:50 +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 21305-07 for ; Thu, 4 Nov 2004 16:23:49 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 793673A48D1 for ; Thu, 4 Nov 2004 16:23:48 +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 iA4GNmJ9023994 for ; Thu, 4 Nov 2004 16:23:48 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id iA4G43oO017358 for pgsql-performance@postgresql.org; Thu, 4 Nov 2004 16:04:03 GMT From: Chris Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Anything to be gained from a 'Postgres Filesystem'? Date: Thu, 04 Nov 2004 10:47:31 -0500 Organization: cbbrowne Computing Inc Lines: 33 Message-ID: <60bred39bg.fsf@dba2.int.libertyrms.com> References: <20041104120047.62810c8f@kingfisher.intern.logi-track.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:S5wKdTs6GNyQ4yoKCVRcJH2vTes= 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/46 X-Sequence-Number: 9000 lists@boutiquenumerique.com (Pierre-Frédéric Caillaud) writes: >> posix_fadvise(2) may be a candidate. Read/Write bareers another pone, as >> well asn syncing a bunch of data in different files with a single call >> (so that the OS can determine the best write order). I can also imagine >> some interaction with the FS journalling system (to avoid duplicate >> efforts). > > There is also the fact that syncing after every transaction > could be changed to syncing every N transactions (N fixed or > depending on the data size written by the transactions) which would > be more efficient than the current behaviour with a sleep. HOWEVER > suppressing the sleep() would lead to postgres returning from the > COMMIT while it is in fact not synced, which somehow rings a huge > alarm bell somewhere. > > What about read order ? > This could be very useful for SELECT queries involving > indexes, which in case of a non-clustered table lead to random seeks > in the table. 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. -- let name="cbbrowne" and tld="cbbrowne.com" in String.concat "@" [name;tld];; http://www.ntlug.org/~cbbrowne/linuxxian.html A VAX is virtually a computer, but not quite.