Re: very long record lines in expanded psql output - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: very long record lines in expanded psql output
Date
Msg-id 7f514232-8e2b-80b7-df2a-d86ea92b4176@dunslane.net
Whole thread Raw
In response to Re: very long record lines in expanded psql output  (Pavel Stehule <pavel.stehule@gmail.com>)
List 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




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: RFC: Improve CPU cache locality of syscache searches
Next
From: Andrew Dunstan
Date:
Subject: Re: very long record lines in expanded psql output