Re: search_path and SET ROLE

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 and SET ROLE
Date: 2024-05-22 19:40:52
Message-ID: CAFj8pRDnocKb-HV=t1Dk1VQa0y2Kh7XBwLz3DjCiMP+_y-UTQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

> On Wed, May 22, 2024 at 2:02 PM Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
> wrote:
>
>> On Wed, 22 May 2024 at 13:48, Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
>> wrote:
>>
>> As a superuser administrator, I need to be able to see ALL tables in ALL
>>> schemas when running "\dt", not just the ones in "$user" and public. And I
>>> need it to act consistently across all the systems.
>>>
>>
>> \dt *.*
>>
>
> Also shows information_schema, pg_catalog, and pg_toast. I can adjust to
> that, though.
>
>
>> But I am skeptical how often you really want this in a real database with
>> more than a few tables. Surely \dn+ followed by \dt [schemaname].* for a
>> few strategically chosen [schemaname] would be more useful?
>>
>
> More than you'd think. I'm always looking up the definition of this table
> or that table (mostly for indices and keys), and I never remember which
> schema they're in.
>

\d *.pg_class

Unfortunately in this case, tab complete doesn't work

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2024-05-22 20:05:32 Re: Missed compiler optimization issue in function select_rtable_names_for_explain
Previous Message Pavel Stehule 2024-05-22 19:38:35 Re: search_path wildcard?