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 4F1613A45F0 for ; Wed, 3 Nov 2004 19:55:22 +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 71488-01 for ; Wed, 3 Nov 2004 19:55:19 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id D9CF03A2B87 for ; Wed, 3 Nov 2004 19:55:20 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iA3JtHC4016199; Wed, 3 Nov 2004 14:55:18 -0500 (EST) To: stuff@opensourceonline.com Cc: pgsql-performance@postgresql.org Subject: Re: preloading indexes In-reply-to: <20041103173054.EJWF21506.fed1rmmtao05.cox.net@CYGNUS> References: <20041103173054.EJWF21506.fed1rmmtao05.cox.net@CYGNUS> Comments: In-reply-to message dated "Wed, 03 Nov 2004 10:30:47 -0700" Date: Wed, 03 Nov 2004 14:55:17 -0500 Message-ID: <16198.1099511717@sss.pgh.pa.us> From: Tom Lane 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/24 X-Sequence-Number: 8978 writes: > I am working with some pretty convoluted queries that work very slowly the > first time they're called but perform fine on the second call. I am fairly > certain that these differences are due to the caching. Can someone point me > in a direction that would allow me to pre-cache the critical indexes? Buy more RAM. Also check your shared_buffers setting (but realize that more is not necessarily better). regards, tom lane