Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mBjok-0006oU-QM for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Aug 2021 20:18:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mBjoj-0000c6-86 for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Aug 2021 20:18:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mBjoj-0000by-00 for pgsql-hackers@lists.postgresql.org; Thu, 05 Aug 2021 20:18:13 +0000 Received: from relay2-d.mail.gandi.net ([217.70.183.194]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mBjog-0007gf-Ex for pgsql-hackers@lists.postgresql.org; Thu, 05 Aug 2021 20:18:12 +0000 Received: (Authenticated sender: adsend@dunslane.net) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id 33AFE40005; Thu, 5 Aug 2021 20:18:07 +0000 (UTC) Subject: Re: very long record lines in expanded psql output To: Pavel Stehule , Platon Pronko Cc: PostgreSQL Hackers References: <998a8549-f808-a349-bae6-9f44d07e050d@dunslane.net> <4e8b9a10-95aa-aecf-01a1-cbc24d643465@gmail.com> From: Andrew Dunstan Message-ID: <7f514232-8e2b-80b7-df2a-d86ea92b4176@dunslane.net> Date: Thu, 5 Aug 2021 16:18:05 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/5/21 2:25 PM, Pavel Stehule wrote: > > > čt 5. 8. 2021 v 18:48 odesílatel Platon Pronko > > 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