Re: Fix how some lists are displayed by psql \d+
| От | Peter Smith |
|---|---|
| Тема | Re: Fix how some lists are displayed by psql \d+ |
| Дата | |
| Msg-id | CAHut+PvfgqAzi_RFhjSJgXMhZSxTqUxhGhmFvYyXsDJebd3Ftg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Fix how some lists are displayed by psql \d+ (Neil Chen <carpenter.nail.cz@gmail.com>) |
| Ответы |
Re: Fix how some lists are displayed by psql \d+
|
| Список | pgsql-hackers |
On Fri, Jan 9, 2026 at 12:19 PM Neil Chen <carpenter.nail.cz@gmail.com> wrote: > ... > This patch looks good to me. > However, referring to the original code implementation, I believe the initial design intention for the psql display wasto make it as "compact" as possible. > I'm not sure.. if it's worthwhile to uniformly change the display style of other items you mentioned (such as Publications)to the compact style? Hi Neil. Thanks for the review and the feedback. I assume the "compactness" you are referring to is where the first item was appearing on the same line as the list header "Partitions:". Yes, I did recognize and consider doing the same for all lists, but it seemed more work, and the end result would *still* have mis-aligned lists whenever there are multiple list types (because those list headers are of all different lengths so the indents are different). IMO that mis-alignment would still look messy just as the current HEAD does. TBH, I don't know if the primary goal of the \d+ is compactness, or readability. I chose readability. YMMV. There might be some middle ground, where lists having just a single item can appear on the same line as their list header. But, with lots of different kinds of lists, all that extra compacting logic seems overkill to me just for the sake of 1 or 2 fewer lines in the \d+ output. Again, that's why I chose the KISS approach. Waiting for other opinions. ====== Kind Regards, Peter Smith. Fujitsu Australia
В списке pgsql-hackers по дате отправления: