From: Tom Lane <tgl@sss.pgh.pa.us>
To: Leif B. Kristensen <leif@solumslekt.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: Error from trigger
Date: Wed, 07 Dec 2005 23:11:19 -0500
Message-ID: <6081.1134015079@sss.pgh.pa.us> (raw)
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>
"Leif B. Kristensen" <leif@solumslekt.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, leif@solumslekt.org
Subject: Re: Error from trigger
In-Reply-To: <6081.1134015079@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox