MIME-Version: 1.0
In-Reply-To: <CANzqJaBoAkdXMkPvdXqhkBduLqpTbU7BdjyZePcuWkFnKi1SDQ@mail.gmail.com>
References: <CANzqJaBoAkdXMkPvdXqhkBduLqpTbU7BdjyZePcuWkFnKi1SDQ@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 22 May 2024 07:47:06 -0700
Message-ID: <CAKFQuwb=HA4=4+DRXYHXNMZiknH_9p6Fp9upSkfw+q1qX_HY1w@mail.gmail.com>
Subject: Re: search_path and SET ROLE
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000031b69706190c0272"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwb%3DHA4%3D4%2BDRXYHXNMZiknH_9p6Fp9upSkfw%2Bq1qX_HY1w%40mail.gmail.com>
Precedence: bulk

--00000000000031b69706190c0272
Content-Type: text/plain; charset="UTF-8"

On Wednesday, May 22, 2024, Ron Johnson <ronljohnsonjr@gmail.com> wrote:
>
>
> It seems that the search_path of the role that you SET ROLE to does not
> become the new search_path.
>
> Am I missing something, or is that PG's behavior?
>

Yes, attaching a setting to a non-login role is basically pointless as
those settings are only applied during the login process.

David J.

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

On Wednesday, May 22, 2024, Ron Johnson &lt;<a href=3D"mailto:ronljohnsonjr=
@gmail.com">ronljohnsonjr@gmail.com</a>&gt; wrote:<blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div dir=3D"ltr"><div><br></div>It seems that the search_path of the =
role that you SET ROLE to does not become the new search_path.<div><br></di=
v><div>Am I missing=C2=A0something, or is that PG&#39;s behavior?</div></di=
v></blockquote><div><br></div><div>Yes, attaching a setting to a non-login =
role is basically pointless as those settings are only applied during the l=
ogin process.</div><div><br></div><div>David J.</div>

--00000000000031b69706190c0272--