Re: search_path wildcard? - Mailing list pgsql-general

From Pavel Stehule
Subject Re: search_path wildcard?
Date
Msg-id CAFj8pRC9_kM_FtQJR4+q2jXH4RqAMUy4Ji=_Fegse+g3tzYzsA@mail.gmail.com
Whole thread Raw
In response to Re: search_path wildcard?  (Ron Johnson <ronljohnsonjr@gmail.com>)
List pgsql-general


st 22. 5. 2024 v 21:13 odesílatel Ron Johnson <ronljohnsonjr@gmail.com> napsal:
On Wed, May 22, 2024 at 1:58 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
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.
 
Missing tables when running "\t" is a bigger hassle.

what is hard on \dt *.*

or you can define own 

 dtall = '\\dt *.*'

:dtall

The problem is not on search path, but maybe on design backslash commands - but there should be some level of consistency

Regards

Pavel

pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: search_path and SET ROLE
Next
From: Pavel Stehule
Date:
Subject: Re: search_path and SET ROLE