I have a behaviour similar to this
http://archives.postgresql.org/pgsql-bugs/2007-09/msg00017.php
create language plpgsql;
create schema test1;
create schema test2;
create table test1.a(a varchar(3) unique);
create table test2.a(a varchar(3) unique);
create or replace function test_insert()
2011/11/7 Ivan Sergio Borgonovo m...@webthatworks.it:
On Mon, 7 Nov 2011 17:55:11 +0100
Pavel Stehule pavel.steh...@gmail.com wrote:
Hello
this is know bug/feature based on caching plans
What puzzled me is I'm operating in a similar way in a different
system and I'm not experiencing the
On Mon, 7 Nov 2011 19:07:29 +0100
Pavel Stehule pavel.steh...@gmail.com wrote:
2011/11/7 Ivan Sergio Borgonovo m...@webthatworks.it:
On Mon, 7 Nov 2011 17:55:11 +0100
Pavel Stehule pavel.steh...@gmail.com wrote:
Hello
this is know bug/feature based on caching plans
What puzzled
On 07/11/11 14:43, Ivan Sergio Borgonovo wrote:
create or replace function test_insert() returns void as
[snip]
$$ language plpgsql volatile;
set search_path to 'test1', 'public';
set search_path to 'test2', 'public';
[snip unexpected behaviour]
I now try to add a SET search_path to
