Re: very long record lines in expanded psql output
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Pavel Stehule <pavel.stehule@gmail.com>,
Platon Pronko <platon7pronko@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-05T20:18:05Z
Lists: pgsql-hackers
On 8/5/21 2:25 PM, Pavel Stehule wrote: > > > čt 5. 8. 2021 v 18:48 odesílatel Platon Pronko > <platon7pronko@gmail.com <mailto:platon7pronko@gmail.com>> napsal: > > 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. > > > it can be a fully new format - designed for simple copy from terminal. > Some like > > ====== record: 10 ====== > ------------ proname ------------ > left > ------------ prosrc ------------ > $lalalal > ewqrwqerw > ewqrwqerqrewq > $ > =============== > > I think that's really a different idea. The original proposal was simply to deal with insanely long header lines. This seems like massive scope creep. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
Commits
-
psql: Tweak xheader_width and pager_min_lines input parsing
- ed7e686a031e 16.0 landed
-
Add xheader_width pset option to psql
- a45388d6e098 16.0 landed