Re: Psql meta-command conninfo+
От | Maiquel Grassi |
---|---|
Тема | Re: Psql meta-command conninfo+ |
Дата | |
Msg-id | CP4P284MB1968F17B9DFA96A5D6529C94ECE72@CP4P284MB1968.BRAP284.PROD.OUTLOOK.COM обсуждение исходный текст |
Ответ на | Re: Psql meta-command conninfo+ (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: Psql meta-command conninfo+
|
Список | pgsql-hackers |
>That leads me to also wonder why don't we change \conninfo to have this
>tabular behavior instead of creating a separate command for it. Why do
>we need to keep the existing form of \conninfo? To me it seems strictly
>less useful, as it is harder to read.
Here, you're suggesting that it would be useful to keep the \conninfo
meta-command, improve it with a "new version," and display the returned
content as a table instead of text. If that's the case, I think it's a good idea
since it would show the "new settings" that the current version doesn't
display and, yes, it would serve the same purpose as \conninfo+.
Regarding which settings to display, the discussion tends to get very broad,
and we can never settle on what should be shown definitively. I believe
that, often, less is more, so showing only the essential settings would be
enough.
Regards,
Maiquel.
>tabular behavior instead of creating a separate command for it. Why do
>we need to keep the existing form of \conninfo? To me it seems strictly
>less useful, as it is harder to read.
Here, you're suggesting that it would be useful to keep the \conninfo
meta-command, improve it with a "new version," and display the returned
content as a table instead of text. If that's the case, I think it's a good idea
since it would show the "new settings" that the current version doesn't
display and, yes, it would serve the same purpose as \conninfo+.
Regarding which settings to display, the discussion tends to get very broad,
and we can never settle on what should be shown definitively. I believe
that, often, less is more, so showing only the essential settings would be
enough.
Regards,
Maiquel.
В списке pgsql-hackers по дате отправления: