Re: plpgsql and intarray extension; int[] - int[] operator does notexist ? - Mailing list pgsql-general

From Merlin Moncure
Subject Re: plpgsql and intarray extension; int[] - int[] operator does notexist ?
Date
Msg-id CAHyXU0zzg_ErWNwzSkNLyzTz4hYP6fObFzMhtJVFDy_VFdzFbQ@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql and intarray extension; int[] - int[] operator does not exist ?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: plpgsql and intarray extension; int[] - int[] operator does not exist ?
List pgsql-general
On Mon, Nov 19, 2018 at 11:56 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> "Day, David" <david.day@redcom.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.

Might be worth considering:
SET LOCAL search_path = whatever

So that LOCAL makes the change local to the transaction.

merlin


pgsql-general by date:

Previous
From: Chris Mair
Date:
Subject: postgresql10-server RPM unpacking of archive failed
Next
From: Tom Lane
Date:
Subject: Re: plpgsql and intarray extension; int[] - int[] operator does not exist ?