RE: plpgsql and intarray extension; int[] - int[] operator does not exist ?

Tom

I was thinking something similar after finding that my test function recreated in the problematic schema would execute correctly
As one user-role but not another and that they had different search_path settings.

After adding public to search patch for that role all was good.

The error message "no operator matches the given name and argument type....." does not make me easily come around to a search path issue.
In any event thanks much for the assistance.

Issue resolved.

Dave

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Monday, November 19, 2018 12:56 PM
To: Day, David <david(dot)day(at)redcom(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: plpgsql and intarray extension; int[] - int[] operator does not exist ?

"Day, David" <david(dot)day(at)redcom(dot)com> writes:
> Any suggestions as to why the int[] operations are not understood in the trigger context.?

The search_path in the trigger probably doesn't include public.
You could add a "SET search_path = whatever" clause to the trigger function definition to ensure it runs with a predictable path.

regards, tom lane