Subject: Re: very long record lines in expanded psql output
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
References: <f03d38a3-db96-a56e-d1bc-dbbc80bbde4d@gmail.com>
 <CAFj8pRBJ8bcTga9qTYG_v25BfeCB=4+GNc1rbf94qex_3C_e-A@mail.gmail.com>
 <998a8549-f808-a349-bae6-9f44d07e050d@dunslane.net>
 <d5280c71-b11b-b0fc-f57d-5033a9197406@gmail.com>
 <bf64d7b0-413d-1501-00b2-992491b865b0@dunslane.net>
 <4e8b9a10-95aa-aecf-01a1-cbc24d643465@gmail.com>
 <CAFj8pRCZwOXDmcHQ5tKt-ukduSRzPmu2-svouCEDQ+LCFXSmfw@mail.gmail.com>
From: Platon Pronko <platon7pronko@gmail.com>
Message-ID: <c084e1fc-0484-1a5e-3645-7c09fdce876a@gmail.com>
Date: Thu, 5 Aug 2021 21:30:43 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: 
 <CAFj8pRCZwOXDmcHQ5tKt-ukduSRzPmu2-svouCEDQ+LCFXSmfw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/c084e1fc-0484-1a5e-3645-7c09fdce876a%40gmail.com>
Precedence: bulk

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 don't think that would be a good idea. If somebody really just needs to copy,
then wrapping the query in "copy (...) to stdout" already works nicely,
no need to create a special mode just for that.
I think the question was more about being able to copy in an ad-hoc way,
in the middle of scrolling trough "normal" output.

Best regards,
Platon Pronko