Re: search_path and SET ROLE

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: search_path and SET ROLE
Дата
Msg-id CAFj8pRDnocKb-HV=t1Dk1VQa0y2Kh7XBwLz3DjCiMP+_y-UTQw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: search_path and SET ROLE  (Ron Johnson <ronljohnsonjr@gmail.com>)
Список pgsql-general


st 22. 5. 2024 v 21:38 odesílatel Ron Johnson <ronljohnsonjr@gmail.com> napsal:
On Wed, May 22, 2024 at 2:02 PM Isaac Morland <isaac.morland@gmail.com> wrote:
On Wed, 22 May 2024 at 13:48, Ron Johnson <ronljohnsonjr@gmail.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

В списке pgsql-general по дате отправления:

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: Re: search_path wildcard?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Missed compiler optimization issue in function select_rtable_names_for_explain