On Mon, Nov 19, 2018 at 11:56 AM Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > > "Day, David" <david.day@xxxxxxxxxx> 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
