Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 9493B9FB701 for ; Mon, 2 Jul 2007 07:05:03 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 36995-02 for ; Mon, 2 Jul 2007 07:04:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id 4C6419FB6AE for ; Mon, 2 Jul 2007 07:04:48 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 268A831422; Mon, 2 Jul 2007 12:04:47 +0200 (MET DST) From: valgog X-Newsgroups: pgsql.performance Subject: [PERFORMANCE] is it possible to force an index to be held in memory? Date: Mon, 02 Jul 2007 10:04:46 -0000 Organization: http://groups.google.com Lines: 15 Message-ID: <1183370686.234761.76720@n60g2000hse.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Complaints-To: groups-abuse@google.com User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4,gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: n60g2000hse.googlegroups.com; posting-host=62.220.8.122; posting-account=VhGBRA0AAAAPUct5VN1tGkfI2QuiqXqC To: pgsql-performance@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.164 tagged_above=0 required=5 tests=AWL=0.163, BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 200707/1 X-Sequence-Number: 25685 Hi, I have found some discussions about that issue, but did not find the answer actually. Is there a way to be sure, that some indexes are alway in memory? My tests bringing them to the memory based file system (ramfs) tablespace showed really a very significant performance gain. But a perspective to have a corrupted database after each machine restart does not really make me feel good. With best regards, -- Valentine Gogichashvili