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 97C293A472F for ; Thu, 4 Nov 2004 00:51:29 +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 53492-09 for ; Thu, 4 Nov 2004 00:51:24 +0000 (GMT) Received: from mail.academyoflearning.ca (s64-180-138-192.bc.hsia.telus.net [64.180.138.192]) by svr1.postgresql.org (Postfix) with ESMTP id CB12A3A470C for ; Thu, 4 Nov 2004 00:51:25 +0000 (GMT) Received: from ipso.snappymail.ca (d207-81-249-35.bchsia.telus.net [207.81.249.35]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.academyoflearning.ca (Postfix) with ESMTP id E220E3E2FE; Wed, 3 Nov 2004 16:50:43 -0800 (PST) Subject: Re: preloading indexes From: Mike Benoit To: Tom Lane Cc: stuff@opensourceonline.com, pgsql-performance@postgresql.org In-Reply-To: <16805.1099515189@sss.pgh.pa.us> References: <20041103201948.HWSQ12834.fed1rmmtao10.cox.net@CYGNUS> <16805.1099515189@sss.pgh.pa.us> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-W5g7jrTRFmZFmIHJ+oeF" Date: Wed, 03 Nov 2004 16:50:42 -0800 Message-Id: <1099529442.18904.4.camel@ipso.snappymail.ca> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1-1mdk X-snappymail-MailScanner-Information: Please contact the ISP for more information X-snappymail-MailScanner: Found to be clean X-snappymail-MailScanner-SpamCheck: not spam, SpamAssassin (score=-0.141, required 5, AWL -0.14, BAYES_44 -0.00) X-MailScanner-From: ipso@snappymail.ca 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/34 X-Sequence-Number: 8988 --=-W5g7jrTRFmZFmIHJ+oeF Content-Type: text/plain Content-Transfer-Encoding: quoted-printable If your running Linux, and kernel 2.6.x, you can try playing with the: /proc/sys/vm/swappiness setting. My understanding is that: echo "0" > /proc/sys/vm/swappiness Will try to keep all in-use application memory from being swapped out when other processes query the disk a lot. Although, since PostgreSQL utilizes the disk cache quite a bit, this may not help you.=20 On Wed, 2004-11-03 at 15:53 -0500, Tom Lane wrote: > writes: > > The caching appears to disappear overnight. >=20 > You've probably got cron jobs that run late at night and blow out your > kernel disk cache by accessing a whole lot of non-Postgres stuff. > (A nightly disk backup is one obvious candidate.) The most likely > solution is to run some cron job a little later to exercise your > database and thereby repopulate the cache with Postgres files before > you get to work ;-) >=20 > regards, tom lane >=20 > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if you= r > joining column's datatypes do not match --=20 Mike Benoit --=-W5g7jrTRFmZFmIHJ+oeF Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBiXzhMhKjsejwBhgRAmZJAJ0W7Fb0+noueiw8SDr0KuH4AII7WgCfY4rR 5YniXISTkAExdNzEb3LFSfY= =Pcfb -----END PGP SIGNATURE----- --=-W5g7jrTRFmZFmIHJ+oeF--