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 21FF03A44F7 for ; Wed, 3 Nov 2004 17:59:06 +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 33060-06 for ; Wed, 3 Nov 2004 17:59:03 +0000 (GMT) Received: from neptune.lgu.ac.uk (neptune.lgu.ac.uk [140.97.30.6]) by svr1.postgresql.org (Postfix) with ESMTP id EFAAD3A4164 for ; Wed, 3 Nov 2004 17:59:02 +0000 (GMT) Received: from solent (cal42-234.lgu.ac.uk [140.97.42.234]) by neptune.lgu.ac.uk (8.12.10/8.12.10) with ESMTP id iA3HwoO6010071; Wed, 3 Nov 2004 17:58:51 GMT Reply-To: From: "Matt Clark" To: , Subject: Re: preloading indexes Date: Wed, 3 Nov 2004 17:59:02 -0000 Organization: Ymogen Ltd Message-ID: <004b01c4c1ce$cd969c80$8300a8c0@solent> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004C_01C4C1CE.CD969C80" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <20041103173054.EJWF21506.fed1rmmtao05.cox.net@CYGNUS> Importance: Normal X-LGU-MailScanner: Found to be clean X-MailScanner-From: matt@ymogen.net X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=HTML_50_60, HTML_FONTCOLOR_BLUE, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200411/17 X-Sequence-Number: 8971 This is a multi-part message in MIME format. ------=_NextPart_000_004C_01C4C1CE.CD969C80 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit The best way to get all the stuff needed by a query into RAM is to run the query. Is it more that you want to 'pin' the data in RAM so it doesn't get overwritten by other queries? -----Original Message----- From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of stuff@opensourceonline.com Sent: 03 November 2004 17:31 To: pgsql-performance@postgresql.org Subject: [PERFORM] preloading indexes 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? ------=_NextPart_000_004C_01C4C1CE.CD969C80 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
The best way to get all the stuff needed by a = query into=20 RAM is to run the query.  Is it more that you want to 'pin' the = data in RAM=20 so it doesn't get overwritten by other=20 queries?
 
-----Original = Message-----
From:=20 pgsql-performance-owner@postgresql.org=20 [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of=20 stuff@opensourceonline.com
Sent: 03 November 2004=20 17:31
To: pgsql-performance@postgresql.org
Subject:=20 [PERFORM] preloading indexes

I am working with some = pretty=20 convoluted queries that work very slowly the first time they’re = called but=20 perform fine on the second call. I am fairly certain that these = differences=20 are due to the caching. Can someone point me in a direction that would = allow=20 me to pre-cache the critical=20 indexes?

------=_NextPart_000_004C_01C4C1CE.CD969C80--