X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 0297D9DCCD0 for ; Thu, 8 Dec 2005 00:11:23 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 69520-02 for ; Thu, 8 Dec 2005 00:11:21 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D58E49DD715 for ; Thu, 8 Dec 2005 00:11:20 -0400 (AST) 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 jB84BJGn006082; Wed, 7 Dec 2005 23:11:19 -0500 (EST) To: "Leif B. Kristensen" cc: pgsql-sql@postgresql.org Subject: Re: Error from trigger In-reply-to: <200512080043.18481.leif@solumslekt.org> References: <200512080006.44606.leif@solumslekt.org> <4507.1133997785@sss.pgh.pa.us> <200512080043.18481.leif@solumslekt.org> Comments: In-reply-to "Leif B. Kristensen" message dated "Thu, 08 Dec 2005 00:43:18 +0100" Date: Wed, 07 Dec 2005 23:11:19 -0500 Message-ID: <6081.1134015079@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.001 required=5 tests=[AWL=0.001] X-Spam-Score: 0.001 X-Spam-Level: X-Archive-Number: 200512/68 X-Sequence-Number: 23610 "Leif B. Kristensen" writes: > On Thursday 08 December 2005 00:23, Tom Lane wrote: >> Offhand this looks like you might have dropped and recreated the >> event_citations table? If so it's just the known problem that >> plpgsql caches plans and doesn't throw them away when the referenced >> objects change. > Right on target. Thank you. A few days ago, as I have already related on > this list, I did the following to fix a bad design with inherited > tables: > ... > I've run a VACUUM FULL ANALYZE, but that doesn't seem to cure the > situation. Is there a way to fix it, short of a full dump, drop, and > reload? Just starting a fresh session should make the problem go away, or if that's not practical update the function definition using ALTER FUNCTION or CREATE OR REPLACE FUNCTION. (You don't need to actually *change* anything about the function, just issue a command that could change it.) If that doesn't make the error go away then we need to look more closely at what's causing it. regards, tom lane