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

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: david(dot)day(at)redcom(dot)com, PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: plpgsql and intarray extension; int[] - int[] operator does not exist ?
Date: 2018-11-19 20:34:32
Message-ID: CAHyXU0zzg_ErWNwzSkNLyzTz4hYP6fObFzMhtJVFDy_VFdzFbQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 19, 2018 at 11:56 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "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.

Might be worth considering:
SET LOCAL search_path = whatever

So that LOCAL makes the change local to the transaction.

merlin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2018-11-19 22:36:51 Re: plpgsql and intarray extension; int[] - int[] operator does not exist ?
Previous Message Chris Mair 2018-11-19 20:15:33 postgresql10-server RPM unpacking of archive failed