Re: patch: psql - enforce constant width of last column

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Ahsan Hadi <ahsan(dot)hadi(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: patch: psql - enforce constant width of last column
Date: 2019-09-27 17:47:33
Message-ID: 20190927174733.GK31412@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 17, 2019 at 05:15:42PM +0200, Pavel Stehule wrote:
>
>
> út 17. 9. 2019 v 17:06 odesílatel Ahsan Hadi <ahsan(dot)hadi(at)gmail(dot)com> napsal:
>
> Hi Pavel,
>
> I have been trying to reproduce the case of badly displaying last columns
> of a query result-set. I played around with the legal values for psql
> border variable but not able to find a case where last columns are badly
> displayed. Can you please share an example that I can use to reproduce this
> problem. I will try out your patch once I am able to reproduce the problem.
>
>
> you need to use pspg, and vertical cursor.
>
> https://github.com/okbob/pspg
> vertical cursor should be active
>
> \pset border 1
> \pset linestyle ascii
> \pset pager always
>
> select * from generate_series(1,3);

I was able to reproduce the failure, but with a little more work:

$ export PSQL_PAGER='pspg --vertical-cursor'
$ psql test
\pset border 1
\pset linestyle ascii
\pset pager always
select * from generate_series(1,3);

Line '1' has highlighted trailing space.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message James Coleman 2019-09-27 17:50:30 Re: [PATCH] Incremental sort (was: PoC: Partial sort)
Previous Message David Steele 2019-09-27 17:01:03 Re: Standby accepts recovery_target_timeline setting?