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 1mBiQ2-0003xE-6V for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Aug 2021 18:48:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mBiQ0-0000Rc-En for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Aug 2021 18:48:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mBiQ0-0000RU-6y for pgsql-hackers@lists.postgresql.org; Thu, 05 Aug 2021 18:48:36 +0000 Received: from mail-lf1-x12e.google.com ([2a00:1450:4864:20::12e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mBiPy-0004Kl-3J for pgsql-hackers@lists.postgresql.org; Thu, 05 Aug 2021 18:48:35 +0000 Received: by mail-lf1-x12e.google.com with SMTP id n17so10324635lft.13 for ; Thu, 05 Aug 2021 11:48:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=tNjLtGGzvItp2qG8PTt8ejtuWRIubYi16tcWiHwMnCc=; b=bzIcZbmQH9liTfTIrIWFEk/BiYHGzQ6SEKqPO2PR7qNSdGRU1Sx6W7YoibcfCa5KxK BGtG6F9q8LgVfwblr4R3/BSlvTs36WYweqpBLMyjPGV2/lWE2frz0ym9YP7sbVwkXCse GFowO2PZMUo6PS9egTfXX7z9LfuzrZqNShFmBFx5RM5u29kIUvw2UzV3iSi6bFU8rYdE VBtf3mMTSUEIOc3m8lFQQy5gsFfArhLM+UHm6ONkJa4DZGxlG8GLtwwYkIN98mywiUfy ReftTsj16UIbPAKMJ5KmLYV0nlBn8lIdeOjLNQ6Eibghe9ugZ11OMSQUjkUTjNq+ZMtt hpYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=tNjLtGGzvItp2qG8PTt8ejtuWRIubYi16tcWiHwMnCc=; b=dv3G2mwhn8/piXIHAsd/xTWfKWeYZqAAitPgH9Wjd8pa5DXpzZLHaRzGVnwGGSb8ft JPutWVexFqUMPzZg9w4rjwh91Kve7uKkg0/nmwrx4aGdmhmG5y+bd6AtClN+xFzwQy87 8rcFrVnp6Yoso2BqJeNNH42gOGRxif4Vzzatk+qwUUqp2JWpQEwV8BO64w1VipvHoJAO w+X/Ghhaf8ubUViMX8WGh5iy/sMHCAkKzFuOZeOnYiUSWQCvL0HOS3aezysRdsgLb6Hk AZVIztFUX5NoYRSD1Tn4pgxgYlcYLXJ45YfwBiIT1BR34dOyjKL2++Tm9zTRQX4pkNBe GF+w== X-Gm-Message-State: AOAM533wkln4aL6mooBlcbdrJsv0P57t62cyQzDlILtc9+FSmVcmnTcL qdFgRvwYJvbsTXDp5vJQRmmQSH4yM64= X-Google-Smtp-Source: ABdhPJwhrf7hsBWXmz636Ixz2X4KENXeP7N0qcCdWzWTTBobvm4C9Qjj/h7ZdZXbO8y3kozCt5ZErQ== X-Received: by 2002:a19:ac45:: with SMTP id r5mr4589860lfc.484.1628189311618; Thu, 05 Aug 2021 11:48:31 -0700 (PDT) Received: from [192.168.1.3] ([46.138.249.39]) by smtp.gmail.com with ESMTPSA id t67sm592734lff.147.2021.08.05.11.48.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 05 Aug 2021 11:48:31 -0700 (PDT) Subject: Re: very long record lines in expanded psql output To: Pavel Stehule Cc: Andrew Dunstan , PostgreSQL Hackers References: <998a8549-f808-a349-bae6-9f44d07e050d@dunslane.net> <4e8b9a10-95aa-aecf-01a1-cbc24d643465@gmail.com> From: Platon Pronko Message-ID: Date: Thu, 5 Aug 2021 21:48:30 +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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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