| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Jan Behrens <jbe-mlist(at)magnetkern(dot)de>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: search_path for PL/pgSQL functions partially cached? |
| Date: | 2025-01-03 21:56:02 |
| Message-ID: | 14e035fb-ab35-4a73-a637-ad0180067b07@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1/3/25 13:33, Jan Behrens wrote:
> On Fri, 3 Jan 2025 10:16:15 -0700
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>
> But if I use "SET search_path FROM CURRENT", then the called function
> won't know the search_path that is set at the caller's side (which is
> what I need to make my interface nice to use).
At this point I am lost as to what the overall goal of this is.
Can you provide a 10000 ft view if what it is you are trying to achieve?
>
> I would prefer my current solution, but I would like to be sure that my
> example (the one in my e-mail dated Fri, 3 Jan 2025 13:53:32 +0100) is
> correct. I still am not sure about that.
>
> Kind Regards,
> Jan Behrens
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-01-03 22:13:58 | Re: search_path for PL/pgSQL functions partially cached? |
| Previous Message | Jan Behrens | 2025-01-03 21:33:12 | Re: search_path for PL/pgSQL functions partially cached? |