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 1mBeQ9-0004pQ-Ln for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Aug 2021 14:32:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mBeQ7-0005Qp-AR for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Aug 2021 14:32:27 +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 1mBeQ6-0005Qh-TB for pgsql-hackers@lists.postgresql.org; Thu, 05 Aug 2021 14:32:26 +0000 Received: from mail-lf1-x132.google.com ([2a00:1450:4864:20::132]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mBeQ0-0002KC-Iu for pgsql-hackers@lists.postgresql.org; Thu, 05 Aug 2021 14:32:25 +0000 Received: by mail-lf1-x132.google.com with SMTP id y34so11480089lfa.8 for ; Thu, 05 Aug 2021 07:32:20 -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=xFoq6qaScdnLvoh2cXECvz8Fn6yCHSFN62t22MAZzXE=; b=kAdpF+z5t7YZkb5NjiVl0Jgq5LNIb8AvLqdC+hNBSc4oa2uxQSAf7fywt2+szszkYU oJ49zflVf84hMoieub6PwLbtg1USFhzDw7p5AxKw/AiWXoyDOahsHzvMWb0GhRxBUF1y 7MgkQAkuGD9PEXqRR5rGBpaadPx1n2TxT+7HTvtK3DbCix+wSCbuPOZ/V57DFMJ8Xf5U Sm+mUxAu77M7FFXnLV3TakXw2kv/nlFW/k6RUsn2CjWhpDBw0TC7o/SKYK0a95kBV0sW txlO0GzaCwIk4YplkwavKFECRWVDR3ZdcMhd1w/BFeXKZs3FaVhOeDKgtH6xIEELp5vu 5/dw== 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=xFoq6qaScdnLvoh2cXECvz8Fn6yCHSFN62t22MAZzXE=; b=mekFzT2IxBEO6WKSH19QDN44fHfbkublNYwTpLlVk0Fxqmf/vg4TVM6xhnAxGqGdao 9hlaQq7fEYIj2rmMinXq1bh+uZjwOTcdIuBnVRt5/SrZVOq8hhCg0R+/h7nKKyMVFwmd G8jOXSdsUU9O+sLeU9ivcOH9M4paDjV7Z12Kik7jT0Nmp1507hCLMrY2yq1NMcFnBi1f BV5Ye8kHKU4lYBP75fikdIVaf3c6BScs2syudtj8FeC6bsRHumY5PHBPQwDzwPDbfFIM wdtKkfSTaPUeXD09XqrTyMfoYGKwE1jsvPh49DrUu7LY4vx1ZkAq4OZabd/utADHXUMM klAw== X-Gm-Message-State: AOAM533wM4nyZ07T2PkOUddB0Wdz8G7vVPfTCLqbruCgznkvidqyC+Vs h0A7vpXhXhrl5ESfJYUlRKeyIvpS4Ss= X-Google-Smtp-Source: ABdhPJz3WwL0+tPKt42nMAKhbHmj+KzT5tLpUso/cTFVpjylV2osr6IkP94XYstoLSKdgVMzpYe/Gg== X-Received: by 2002:a05:6512:20d9:: with SMTP id u25mr3982035lfr.463.1628173938927; Thu, 05 Aug 2021 07:32:18 -0700 (PDT) Received: from [192.168.1.3] ([46.138.249.39]) by smtp.gmail.com with ESMTPSA id a1sm423739ljj.97.2021.08.05.07.32.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 05 Aug 2021 07:32:18 -0700 (PDT) Subject: Re: very long record lines in expanded psql output To: Pavel Stehule Cc: PostgreSQL Hackers References: <27f30f68-c4bd-2f02-080c-8feb0b6eded3@gmail.com> From: Platon Pronko Message-ID: <0618f78d-070a-899d-10d4-73161e5de184@gmail.com> Date: Thu, 5 Aug 2021 17:32:17 +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! My apologies - I was using pspg incorrectly. If it's called via the pipe then all the column wrapping is ignored, and that's why I couldn't reproduce the issues. If instead pspg is used via "\setenv PAGER pspg", then I indeed can't scroll the table horizontally more than 1 character, and that's definitely broken. I'll be using "\pset format wrapped" from now on, it's good enough. My only issue would be with copying the long cell contents, but that's an uncommon case and can be worked around without too much trouble. Best regards, Platon Pronko