MIME-Version: 1.0
References: <20241227205025.1d059f72c7c08d23c9648c26@magnetkern.de>
 <CAKFQuwb4hgHH=Z6cx5Hh_qc10TCYMb1QVfP3099X1Psmyw0r3Q@mail.gmail.com>
 <20241228004009.267f21b78394c934f27f9974@magnetkern.de> <20250103135332.7910a008714abaa04d32e5e2@magnetkern.de>
 <CAKFQuwaU19_6HaB+9-L-fQhjUr8_5ACvxLAPRBhEdfLv9JVZBg@mail.gmail.com>
 <20250103174849.f071d9c6942f76a9b812157c@magnetkern.de> <CAKFQuwZdt+YLi=9_WraRLajuOkmw4esFzbHTXmv5MwHJemdDhQ@mail.gmail.com>
 <20250103223312.dde69ae482776e4f1b0c2258@magnetkern.de> <14e035fb-ab35-4a73-a637-ad0180067b07@aklaver.com>
 <20250104002203.2aed83d48d795ce6fbbd3b61@magnetkern.de>
In-Reply-To: <20250104002203.2aed83d48d795ce6fbbd3b61@magnetkern.de>
From: Isaac Morland <isaac.morland@gmail.com>
Date: Fri, 3 Jan 2025 18:36:13 -0500
Message-ID: <CAMsGm5fVJzOZ6kNDwkiRuFZFW=cY=FZixaSOd=WRdP0QLdoqew@mail.gmail.com>
Subject: Re: search_path for PL/pgSQL functions partially cached?
To: Jan Behrens <jbe-mlist@magnetkern.de>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>, 
	"David G. Johnston" <david.g.johnston@gmail.com>, 
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000043620d062ad5bffa"
Archived-At: <https://www.postgresql.org/message-id/CAMsGm5fVJzOZ6kNDwkiRuFZFW%3DcY%3DFZixaSOd%3DWRdP0QLdoqew%40mail.gmail.com>
Precedence: bulk

--00000000000043620d062ad5bffa
Content-Type: text/plain; charset="UTF-8"

On Fri, 3 Jan 2025 at 18:22, Jan Behrens <jbe-mlist@magnetkern.de> wrote:


> Instead, I plan to expect the function to receive a query string that
> will get the data that is being processed by the function.
>
> That query string should be allowed to refer to tables in the
> search_path at the caller's side.
>
> Therefore, I cannot use the "SET search_path FROM CURRENT" in my
> "CREATE FUNCTION" statement, because it would overwrite the current
> search_path on each call of the function.
>

 I wonder if it would help if EXECUTE took an optional search_path to use
while executing the query.

--00000000000043620d062ad5bffa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, 3 Jan 2025 at 18:22, Jan Behrens =
&lt;<a href=3D"mailto:jbe-mlist@magnetkern.de">jbe-mlist@magnetkern.de</a>&=
gt; wrote:<br></div><div class=3D"gmail_quote gmail_quote_container"><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(20=
4,204,204);padding-left:1ex">
Instead, I plan to expect the function to receive a query string that<br>
will get the data that is being processed by the function.<br>
<br>
That query string should be allowed to refer to tables in the<br>
search_path at the caller&#39;s side.<br>
<br>
Therefore, I cannot use the &quot;SET search_path FROM CURRENT&quot; in my<=
br>
&quot;CREATE FUNCTION&quot; statement, because it would overwrite the curre=
nt<br>
search_path on each call of the function.<br></blockquote><div><br></div><d=
iv>=C2=A0I wonder if it would help if EXECUTE took an optional search_path =
to use while executing the query.</div><div><br></div></div></div>

--00000000000043620d062ad5bffa--