Tom Lane wrote: > I'm convinced that 8.3 has the same bug, in the sense that it could fail > this way if it had to revalidate a cached plan. Probably the reason you > didn't see it before is that 8.4 has more conditions in which it will > invalidate cached plans. In particular, is it possible that this > failure occurs when you try to call a plpgsql function that has just > been replaced via CREATE OR REPLACE FUNCTION?
Do we have the stuff where an ANALYZE could invalidate cached plans? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
