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 0B4923A4665 for ; Wed, 3 Nov 2004 20:53:13 +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 89710-02 for ; Wed, 3 Nov 2004 20:53:10 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 930173A4657 for ; Wed, 3 Nov 2004 20:53:10 +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 iA3Kr9Vt016806; Wed, 3 Nov 2004 15:53:10 -0500 (EST) To: stuff@opensourceonline.com Cc: pgsql-performance@postgresql.org Subject: Re: preloading indexes In-reply-to: <20041103201948.HWSQ12834.fed1rmmtao10.cox.net@CYGNUS> References: <20041103201948.HWSQ12834.fed1rmmtao10.cox.net@CYGNUS> Comments: In-reply-to message dated "Wed, 03 Nov 2004 13:19:43 -0700" Date: Wed, 03 Nov 2004 15:53:09 -0500 Message-ID: <16805.1099515189@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/27 X-Sequence-Number: 8981 writes: > The caching appears to disappear overnight. 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 ;-) regards, tom lane