Tom Lane wrote:
Joe Maldonado <[EMAIL PROTECTED]> writes:
After a create or replace view, the new view definition is not being
used by plpgsql functions that use the view. Is this a known bug ? Is
there a workaround it ?
Start a fresh backend session. The old query plan is presumably being
Joe Maldonado <[EMAIL PROTECTED]> writes:
> After a create or replace view, the new view definition is not being
> used by plpgsql functions that use the view. Is this a known bug ? Is
> there a workaround it ?
Start a fresh backend session. The old query plan is presumably being
cached by plpgsq
After a create or replace view, the new view definition is not being
used by plpgsql functions that use the view. Is this a known bug ? Is
there a workaround it ?
For instance, selecting from afunc() still returns the old view's results.
create table c ( a int );
create or replace view a as select
