pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Platon Pronko <platon7pronko@gmail.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: very long record lines in expanded psql output
Date: Thu, 5 Aug 2021 21:48:30 +0300
Message-ID: <c0113fed-3a16-48af-135e-a9ad33ea6238@gmail.com> (raw)
In-Reply-To: <CAFj8pRB+fu_GfZmw4WpO-qp+K4UnHE0q2NSkkvs=oxBndgNurA@mail.gmail.com>
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>
	<c084e1fc-0484-1a5e-3645-7c09fdce876a@gmail.com>
	<CAFj8pRB+fu_GfZmw4WpO-qp+K4UnHE0q2NSkkvs=oxBndgNurA@mail.gmail.com>

Hi!

>> 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.
>>
> 
> It is working well, but it is copy to file, not copy to clipboard.

Maybe I misunderstood - are you suggesting this a special mode in pspg? I thought
that you were suggesting to implement a mode in psql, something like
"\pset format_for_clipboard".
  
>> I think the question was more about being able to copy in an ad-hoc way,
>> in the middle of scrolling trough "normal" output.
> 
> I understand your motivation, but I don't feel a significant benefit to
> increase the complexity of the main format (more, when it breaks pspg,
> without possibility to fix it). but it can depend on usual data, and it is
> true, so when I use pspg, I don't use extended mode too often.

To clarify: I'm not suggesting my patch anymore - it definitely breaks pspg and this
is completely unacceptable.
We're just discussing the possible alternate solutions, I think.

Best regards,
Platon Pronko





view thread (39+ messages)  latest in thread

Message-ID: <c0113fed-3a16-48af-135e-a9ad33ea6238@gmail.com>
Permalink:  ../c0113fed-3a16-48af-135e-a9ad33ea6238@gmail.com/
Also on:    postgresql.org/message-id/c0113fed-3a16-48af-135e-a9ad33ea6238@gmail.com

 · 

reply
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, pavel.stehule@gmail.com, andrew@dunslane.net, pgsql-hackers@lists.postgresql.org
  Subject: Re: very long record lines in expanded psql output
  In-Reply-To: <c0113fed-3a16-48af-135e-a9ad33ea6238@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