Re: search_path wildcard?

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: search_path wildcard?
Date: 2024-05-22 19:38:35
Message-ID: CAFj8pRC9_kM_FtQJR4+q2jXH4RqAMUy4Ji=_Fegse+g3tzYzsA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

st 22. 5. 2024 v 21:13 odesílatel Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
napsal:

> On Wed, May 22, 2024 at 1:58 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Ron Johnson <ronljohnsonjr(at)gmail(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2024-05-22 19:40:52 Re: search_path and SET ROLE
Previous Message Ron Johnson 2024-05-22 19:38:30 Re: search_path and SET ROLE