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

From David G. Johnston
Subject Re: search_path for PL/pgSQL functions partially cached?
Date
Msg-id CAKFQuwb1BpvArobDRJpgGFFWTDqg+2Dmstrf8MnmuM68BxXMKg@mail.gmail.com
Whole thread Raw
In response to Re: search_path for PL/pgSQL functions partially cached?  (Jan Behrens <jbe-mlist@magnetkern.de>)
List pgsql-general
On Fri, Jan 3, 2025 at 2:33 PM Jan Behrens <jbe-mlist@magnetkern.de> wrote:
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.


If it does what you want and it is only ever executed by application code over a client connection you should be fine.  Your client connection will always have whatever search_path you arrange to have in place and the application developer will know whether their environment is correct or not when they test it, and have the ability to change their environment as needed.

David J.

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: search_path for PL/pgSQL functions partially cached?
Next
From: Jan Behrens
Date:
Subject: Re: search_path for PL/pgSQL functions partially cached?