Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 90E0A9FB22E for ; Thu, 17 May 2007 05:55:12 -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 23662-05 for ; Thu, 17 May 2007 05:54:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 2D1B59FB586 for ; Thu, 17 May 2007 05:55:09 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from joshua.dreamthought.com (joshua.dreamthought.com [193.201.200.96]) by svr4.postgresql.org (Postfix) with ESMTP id C7DF25AF884 for ; Thu, 17 May 2007 08:34:05 +0000 (GMT) Received: from rafiq (helo=localhost) by joshua.dreamthought.com with local-esmtp (Exim 4.66 ()) (envelope-from ) id 1HobTC-000I3m-9Z for pgsql-admin@postgresql.org; Thu, 17 May 2007 09:36:22 +0100 Date: Thu, 17 May 2007 09:36:22 +0100 (BST) From: Raf To: pgsql-admin@postgresql.org Subject: [OT] Flushing Postgres Function Cache Message-ID: <20070517092853.R69332@joshua.dreamthought.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: rafiq@joshua.dreamthought.com X-SA-Exim-Scanned: No (on joshua.dreamthought.com); SAEximRunCond expanded to false X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/153 X-Sequence-Number: 25473 Greetings, In the face of shabby google results, I hoped that someone hear might know something about the postgres function cache. We have a server which reports an error of the form "cache lookup failed for function ." Initially, I'd hoped to resolve this without a restart (which didn't do the trick either), and had been searching for some way to clear postgres' internal function cache - I think it stores plans/hints/compiled-version relating to stored proc's? I tried to select the reported oid out of pg_proc, which resulted in an empty set. I then went on to explicitly drop the function and recreate it. This was interspersed with numerous postgres restarts and dropping of all client connections. In spite of this I still get the same error from our client which still reports the same OID; which doesn't exist in pg_proc. In any case, I can't seem to find any documentation which tells me how to clear this cache. Versions: pg: postgresql v 8.0.1-r4 os: Gentoo Linux/Kernel 2.6.12.5 #1 Any help would be of value? Cheers, Raf