Обсуждение: [GENERAL] Long wrapped header lines in psql with expanded mode (9.6.3)
Hello, I'm using the following minimal ~/.psqlrc: \pset expanded on Now when I select rows from a table which are too long to fit the screen then I get this output: simon=> table test; -[ RECORD 1 ]--------------------------------------- ---------------------------------------------------- ---------------------------------------------------- ------------------------------------------------- test | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -[ RECORD 2 ]--------------------------------------- ---------------------------------------------------- ---------------------------------------------------- ------------------------------------------------- test | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Is there any way to remove the superfluous header lines? I'd like to get the following output which doesn't waste so much screen space: simon=> table test; -[ RECORD 1 ]--------------------------------------- test | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -[ RECORD 2 ]--------------------------------------- test | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Regards Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9
Вложения
2017-07-13 14:40 GMT+02:00 Simon Ruderich <simon@ruderich.org>:
Hello,
I'm using the following minimal ~/.psqlrc:
\pset expanded on
Now when I select rows from a table which are too long to fit the
screen then I get this output:
simon=> table test;
-[ RECORD 1 ]---------------------------------------
----------------------------------------------------
----------------------------------------------------
-------------------------------------------------
test | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
-[ RECORD 2 ]---------------------------------------
----------------------------------------------------
----------------------------------------------------
-------------------------------------------------
test | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Is there any way to remove the superfluous header lines? I'd like
to get the following output which doesn't waste so much screen
space:
simon=> table test;
-[ RECORD 1 ]---------------------------------------
test | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
-[ RECORD 2 ]---------------------------------------
test | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Regards
Simon
what about \pset format wrapped
Regards
Pavel
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
On Thu, Jul 13, 2017 at 04:05:43PM +0200, Pavel Stehule wrote: > what about \pset format wrapped I prefer the extended format which I find more pleasant to read. I'm just curious if this expected behavior or a bug / weird effect of my setup. If it's considered a bug I'd by willing to try to come up with a patch (I already have a hacky version running on my local machine which fixes it for my use case). Regards Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9