Re: Remove source code display from \df+?

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: Remove source code display from \df+?
Дата
Msg-id CAFj8pRA7rYzNXhx2MJbEsdZEmKvPjjsRC0b0rH81iLpEYwVf+A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Remove source code display from \df+?  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: Remove source code display from \df+?  (Isaac Morland <isaac.morland@gmail.com>)
Список pgsql-hackers


st 11. 1. 2023 v 18:25 odesílatel Magnus Hagander <magnus@hagander.net> napsal:


On Wed, Jan 11, 2023 at 6:19 PM Pavel Stehule <pavel.stehule@gmail.com> wrote:


st 11. 1. 2023 v 17:50 odesílatel Isaac Morland <isaac.morland@gmail.com> napsal:
I find \df+ much less useful than it should be because it tends to be cluttered up with source code. Now that we have \sf, would it be reasonable to remove the source code from the \df+ display? This would make it easier to see function permissions and comments. If somebody wants to see the full definition of a function they can always invoke \sf on it.

If there is consensus on the idea in principle I will write up a patch.

+1


+1 but maybe with a twist. For any functions in a procedural language like plpgsql, it makes it pretty useless today. But when viewing an internal or C language function, it's short enough and still actually useful. Maybe some combination where it would keep showing those for such language, but would show "use \sf to view source" for procedural languages?

yes, it is almost necessary for C functions or functions in external languages. Maybe it can be specified in pg_language if prosrc is really source code or some reference.



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

Предыдущее
От: Jacob Champion
Дата:
Сообщение: Re: [PATCH] Add `verify-system` sslmode to use system CA pool for server cert
Следующее
От: Nathan Bossart
Дата:
Сообщение: Re: fix and document CLUSTER privileges