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 CAHyXU0yAfNckidGXivQ0oZ5crEPg74auWLG7MeUM3-x99qD+qA@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>)
List pgsql-general
On Mon, Nov 19, 2018 at 4:36 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Merlin Moncure <mmoncure@gmail.com> writes:
> > On Mon, Nov 19, 2018 at 11:56 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> 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.
>
> What I was suggesting was to create the trigger function using
>
> create function ... as $$ ...body... $$ set search_path = whatever;
>
> That makes the setting local to each function call.

Oh, I see.  Yes, that's even better.

merlin


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: plpgsql and intarray extension; int[] - int[] operator does not exist ?
Next
From: Wyatt Alt
Date:
Subject: replication lag despite corrective config