| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jan Behrens <jbe-mlist(at)magnetkern(dot)de> |
| 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 22:13:58 |
| Message-ID: | CAKFQuwb1BpvArobDRJpgGFFWTDqg+2Dmstrf8MnmuM68BxXMKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jan 3, 2025 at 2:33 PM Jan Behrens <jbe-mlist(at)magnetkern(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Behrens | 2025-01-03 23:22:03 | Re: search_path for PL/pgSQL functions partially cached? |
| Previous Message | Adrian Klaver | 2025-01-03 21:56:02 | Re: search_path for PL/pgSQL functions partially cached? |