Re: very long record lines in expanded psql output

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Platon Pronko <platon7pronko(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: very long record lines in expanded psql output
Date: 2021-08-05 20:18:05
Message-ID: 7f514232-8e2b-80b7-df2a-d86ea92b4176@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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(at)gmail(dot)com <mailto:platon7pronko(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2021-08-05 20:19:03 Re: very long record lines in expanded psql output
Previous Message Andres Freund 2021-08-05 20:12:01 Re: RFC: Improve CPU cache locality of syscache searches