Re: BUG #5902: pl/pgsql plans are not invalidated on discard all - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5902: pl/pgsql plans are not invalidated on discard all
Date
Msg-id 7481.1298907876@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5902: pl/pgsql plans are not invalidated on discard all  ("Ingmar Brouns" <swingi@gmail.com>)
Responses Re: BUG #5902: pl/pgsql plans are not invalidated on discard all  (Ingmar Brouns <swingi@gmail.com>)
List pgsql-bugs
"Ingmar Brouns" <swingi@gmail.com> writes:
> Description:        pl/pgsql plans are not invalidated on discard all

Yes they are.

> I ran into the pl/pgsql Plan Invalidation and search_path bug that is on the
> todo list

> http://wiki.postgresql.org/wiki/Todo#PL.2FpgSQL

> I was looking for a workaround to this problem, and figured that calling
> 'discard all', or 'discard plans' should do the trick.

That's not a solution because the plancache module intentionally
preserves the original search_path value while replanning.  This
may not be what you wished for, but it's operating as intended,
and changing it would break other use-cases that work today.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Ingmar Brouns"
Date:
Subject: BUG #5902: pl/pgsql plans are not invalidated on discard all
Next
From: "Kevin Grittner"
Date:
Subject: Re: BUG #5896: When server cannot be started, first it says that it couldn't be started and then Server Started