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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Day, David" <david(dot)day(at)redcom(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: plpgsql and intarray extension; int[] - int[] operator does not exist ?
Date: 2018-11-19 17:56:19
Message-ID: 15705.1542650179@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Day, David 2018-11-19 19:38:58 RE: plpgsql and intarray extension; int[] - int[] operator does not exist ?
Previous Message Magnus Hagander 2018-11-19 17:47:03 Re: pgconf eu 2018 slides entry missing from https://wiki.postgresql.org/wiki/PostgreSQL_Related_Slides_and_Presentations