Re: search_path for PL/pgSQL functions partially cached? - Mailing list pgsql-general

From Adrian Klaver
Subject Re: search_path for PL/pgSQL functions partially cached?
Date
Msg-id 14e035fb-ab35-4a73-a637-ad0180067b07@aklaver.com
Whole thread Raw
In response to Re: search_path for PL/pgSQL functions partially cached?  (Jan Behrens <jbe-mlist@magnetkern.de>)
Responses Re: search_path for PL/pgSQL functions partially cached?
List pgsql-general
On 1/3/25 13:33, Jan Behrens wrote:
> On Fri, 3 Jan 2025 10:16:15 -0700
> "David G. Johnston" <david.g.johnston@gmail.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.klaver@aklaver.com




pgsql-general by date:

Previous
From: Jan Behrens
Date:
Subject: Re: search_path for PL/pgSQL functions partially cached?
Next
From: "David G. Johnston"
Date:
Subject: Re: search_path for PL/pgSQL functions partially cached?