From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron Johnson <ronljohnsonjr@gmail.com>
cc: pgsql-general <pgsql-general@postgresql.org>
Subject: Re: search_path wildcard?
In-reply-to: <CANzqJaCjWr3Z3typ-Ye8vitiiYQEkCGz=w4Sx9Up7dZ+Hsb6Fw@mail.gmail.com>
References: <CANzqJaDxVFRPreSz_e=cg2PU2nW48BUcoJTyvc72Yry0tqkTcQ@mail.gmail.com> <CAKFQuwZx0G=0fPDmhwWiCNT1+ZUWYQGkYVj5Vab10A0_bksq0g@mail.gmail.com> <CANzqJaCjWr3Z3typ-Ye8vitiiYQEkCGz=w4Sx9Up7dZ+Hsb6Fw@mail.gmail.com>
Comments: In-reply-to Ron Johnson <ronljohnsonjr@gmail.com>
	message dated "Wed, 22 May 2024 13:54:21 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4178923.1716400730.1@sss.pgh.pa.us>
Date: Wed, 22 May 2024 13:58:50 -0400
Message-ID: <4178924.1716400730@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/4178924.1716400730%40sss.pgh.pa.us>
Precedence: bulk

Ron Johnson <ronljohnsonjr@gmail.com> writes:
> That would be a helpful feature for administrators, when there are multiple
> schemas in multiple databases, on multiple servers: superusers get ALTER
> ROLE foo SET SEARCH_PATH  = '*'; and they're done with it.

... and they're pwned within five minutes by any user with the wits
to create a trojan-horse function or operator.  Generally speaking,
you want admins to run with a minimal search path not a maximal one.

			regards, tom lane