| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: search_path wildcard? |
| Date: | 2024-05-22 19:34:39 |
| Message-ID: | CAFj8pRDg0UGkG9=LVRL2-mmJRTK2_KkEuzvzgBRqVDP2LZiR_A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
st 22. 5. 2024 v 19:54 odesílatel Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
napsal:
> On Wed, May 22, 2024 at 12:53 PM David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> On Wed, May 22, 2024, 10:36 Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
>>
>>> This doesn't work, and I've found nothing similar:
>>> ALTER ROLE foo SET SEARCH_PATH = '*';
>>>
>>
>> Correct, you cannot do that.
>>
>
> 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.
>
It can be pretty dangerous, because you don't specify order of schemas
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-05-22 19:38:30 | Re: search_path and SET ROLE |
| Previous Message | Ron Johnson | 2024-05-22 19:12:50 | Re: search_path wildcard? |