Re: BUG #6517: Volatile function erroneously optimized, does not consider change in schema path - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #6517: Volatile function erroneously optimized, does not consider change in schema path
Date
Msg-id CA+Tgmoa+HMFSbV9hZSTaO80AusxY1TFcrzQ-DCpg+jBO=Pq8+g@mail.gmail.com
Whole thread Raw
In response to BUG #6517: Volatile function erroneously optimized, does not consider change in schema path  (rene.vanpaassen@gmail.com)
Responses Re: BUG #6517: Volatile function erroneously optimized, does not consider change in schema path
List pgsql-bugs
On Mon, Mar 5, 2012 at 6:52 AM,  <rene.vanpaassen@gmail.com> wrote:
> I found some unexpected behaviour when changing the schema search path in
> combination with plpgsql functions (may be true for other function types
> too, did not check). This occurs both in 9.1.2 (on Fedora, 64 bit) and 8.4.9
> (Centos 6, 32 bit). I created a small example run with psql, to demonstrate
> this.

I have a vague feeling this is a known issue.  It sure seems like we
should handle it better, but I'm not sure how hard that would be to
implement.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: postgresql 9.1 replicaiton query ( GNU/Linux replicate to Windows)
Next
From: Robert Haas
Date:
Subject: Re: BUG #6513: explain (analyze, buffers) and toasted fields