Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id EC06F9FBD2E for ; Wed, 23 May 2007 20:17:09 -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 53628-02 for ; Wed, 23 May 2007 20:17:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A87A09FB40D for ; Wed, 23 May 2007 20:17:05 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l4NNGw5d025879; Wed, 23 May 2007 19:16:58 -0400 (EDT) To: John Summerfield cc: pgsql-sql@postgresql.org Subject: Re: FATAL: cache lookup failed for function 1003 In-reply-to: <4654C7B2.8020507@herakles.homelinux.org> References: <4654446C.5040504@herakles.homelinux.org> <20070523203701.GH13250@alvh.no-ip.org> <4654C7B2.8020507@herakles.homelinux.org> Comments: In-reply-to John Summerfield message dated "Thu, 24 May 2007 07:01:06 +0800" Date: Wed, 23 May 2007 19:16:58 -0400 Message-ID: <25878.1179962218@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/163 X-Sequence-Number: 28443 John Summerfield writes: > That (combined with another cvs update) cleared the problem. Should the > distclean be necessary? Yes, unless you configured with --enable-depend during your previous build (and I wouldn't necessarily swear that --enable-depend catches every possible dependency). When in doubt --- especially if your build fails but the buildfarm seems happy --- do a distclean & rebuild before investing any intellectual effort in figuring out the problem. My own practice, developed after a couple of unpleasant episodes of this sort, is to make distclean before any cvs update. Machine cycles are cheap, my time isn't. I've found that I can generally overlap the rebuild time with useful work, or at least mail-reading ... regards, tom lane