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

From: Ahsan Hadi <ahsan(dot)hadi(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: patch: psql - enforce constant width of last column
Date: 2019-09-17 15:06:09
Message-ID: CA+9bhCKY1csVb_s7TJYbgPu-HhfNH5wfC0QsQO6DNOsmoWx88g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Thanks,

-- Ahsan

On Mon, Sep 9, 2019 at 2:32 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:

> Hi
>
> When I played with vertical cursor support I got badly displayed last
> columns when border was not 2. Only when border is 2, then psql displays
> last column with same width for each row.
>
> I think so we can force column width alignment for any border styles today
> (for alignment and wrapping styles) or as minimum this behave can be
> optional.
>
> I wrote a patch with pset option "final_spaces", but I don't see a reason
> why we trim rows today.
>
> Regards
>
> Pavel
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2019-09-17 15:07:43 Re: Feature request: binary NOTIFY
Previous Message Robert Haas 2019-09-17 14:55:04 Re: block-level incremental backup