From: Platon Pronko <platon7pronko@gmail.com>
To: Andrew Dunstan <andrew@dunslane.net>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: very long record lines in expanded psql output
Date: Thu, 5 Aug 2021 19:48:13 +0300
Message-ID: <4e8b9a10-95aa-aecf-01a1-cbc24d643465@gmail.com> (raw)
In-Reply-To: <bf64d7b0-413d-1501-00b2-992491b865b0@dunslane.net>
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>
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.
Best regards,
Platon Pronko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: platon7pronko@gmail.com, andrew@dunslane.net, pavel.stehule@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: very long record lines in expanded psql output
In-Reply-To: <4e8b9a10-95aa-aecf-01a1-cbc24d643465@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox