Re: very long record lines in expanded psql output
От | Platon Pronko |
---|---|
Тема | Re: very long record lines in expanded psql output |
Дата | |
Msg-id | 0efd52b9-450a-7636-fb75-663bc2d81b34@gmail.com обсуждение исходный текст |
Ответ на | Re: very long record lines in expanded psql output (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: very long record lines in expanded psql output
|
Список | pgsql-hackers |
Hi! >>>>> I also find this annoying and would be happy to be rid of it. >>>> >>>> Have you tried "\pset format wrapped"? Pavel suggested it, and it >>>> solved most of the problem for me, for example. >>> >>> Yes, but it changes the data line output. Ideally, you should be able >>> to modify these independently. >> >> I agree, and I think this can be implemented, but I'm a bit afraid of >> introducing an additional psql option (there's already quite a lot of >> them). >> I suspect primary PostgreSQL maintainers won't be happy with such an >> approach. >> >> > > I think I qualify as one of those ... :-) Sorry, I'm new here, don't know who's who :) I'll start working on a new patch then. A couple questions about specifics: 1. Can we add "expanded" in the option name, like "xheader_expanded_width"? I think adjusting the header row width doesn't make sense on any other modes, and placing that in the option name makes intent a bit clearer. 2. What was "column" option in your original suggestion supposed to do? ("\pset xheader_width column|page|nnn") 3. Should we bother with using this option when in "\pset border 2" mode? I can do it for consistency, but it will still look bad. Best regards, Platon Pronko
В списке pgsql-hackers по дате отправления: