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 23:06:58 |
Message-ID: | CAHyXU0yAfNckidGXivQ0oZ5crEPg74auWLG7MeUM3-x99qD+qA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Nov 19, 2018 at 4:36 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> > On Mon, Nov 19, 2018 at 11:56 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Wyatt Alt | 2018-11-20 01:46:55 | replication lag despite corrective config |
Previous Message | Tom Lane | 2018-11-19 22:36:51 | Re: plpgsql and intarray extension; int[] - int[] operator does not exist ? |