X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5C1FB529D7 for ; Tue, 28 Jun 2005 10:10: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 22397-10 for ; Tue, 28 Jun 2005 13:10:56 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by svr1.postgresql.org (Postfix) with SMTP id 04B04529C8 for ; Tue, 28 Jun 2005 10:10:54 -0300 (ADT) Received: (qmail invoked by alias); 28 Jun 2005 13:10:56 -0000 Received: from dsl-082-083-232-093.arcor-ip.net (EHLO colt.pezone.net) [82.83.232.93] by mail.gmx.net (mp018) with SMTP; 28 Jun 2005 15:10:56 +0200 X-Authenticated: #495269 From: Peter Eisentraut To: =?iso-8859-1?q?K=D6PFERL_Robert?= Subject: Re: Direct I/O versus OS-Caching Date: Tue, 28 Jun 2005 15:10:53 +0200 User-Agent: KMail/1.8.1 Cc: pgsql-admin@postgresql.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200506281510.54832.peter_e@gmx.net> X-Y-GMX-Trusted: 0 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.037 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200506/256 X-Sequence-Number: 18011 KÖPFERL Robert wrote: > What's the better/faster alternative? > Enabling OS-file system caching or disabling it and forcing direct > I/O? PostgreSQL is designed to rely on OS file-system caching, so you better not turn that off. -- Peter Eisentraut http://developer.postgresql.org/~petere/