Re: BUG #5902: pl/pgsql plans are not invalidated on discard all

From: Ingmar Brouns <swingi(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5902: pl/pgsql plans are not invalidated on discard all
Date: 2011-03-01 11:11:56
Message-ID: AANLkTi=gKPCOKq4RPBNRS-K=3fQj+oD06m2Dfmy=T-0A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Merlin Moncure 2011-03-01 15:01:00 Re: BUG #5902: pl/pgsql plans are not invalidated on discard all
Previous Message Sarp Akal 2011-03-01 06:59:47 BUG #5903: Turkish encoding problem