| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ingmar Brouns" <swingi(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5902: pl/pgsql plans are not invalidated on discard all |
| Date: | 2011-02-28 15:44:36 |
| Message-ID: | 7481.1298907876@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Ingmar Brouns" <swingi(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nacho Mezzadra | 2011-02-28 19:08:09 | Re: BUG #5896: When server cannot be started, first it says that it couldn't be started and then Server Started |
| Previous Message | Ingmar Brouns | 2011-02-28 14:09:57 | BUG #5902: pl/pgsql plans are not invalidated on discard all |