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

From Ingmar Brouns
Subject Re: BUG #5902: pl/pgsql plans are not invalidated on discard all
Date
Msg-id AANLkTi=gKPCOKq4RPBNRS-K=3fQj+oD06m2Dfmy=T-0A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #5902: pl/pgsql plans are not invalidated on discard all  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5902: pl/pgsql plans are not invalidated on discard all  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-bugs
Hi Tom,

thanks for your reply.


> > 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
>

We are weighing our options to deal with this problem.
I'm very interested in the use cases that  will break when using the
current search_path instead of the original search_path when replanning.
Can you tell me what will break?

Thanks,

Ingmar

pgsql-bugs by date:

Previous
From: "Sarp Akal"
Date:
Subject: BUG #5903: Turkish encoding problem
Next
From: Merlin Moncure
Date:
Subject: Re: BUG #5902: pl/pgsql plans are not invalidated on discard all