Re: \pset xheader_width page as default? (Re: very long record lines in expanded psql output)

From: Christoph Berg <myon(at)debian(dot)org>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Platon Pronko <platon7pronko(at)gmail(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: \pset xheader_width page as default? (Re: very long record lines in expanded psql output)
Date: 2022-08-30 14:36:49
Message-ID: Yw4ggV8NXGV9SXXb@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: Pavel Stehule
> pspg requires all lines to have the same width. It can do some corrections
> - but it is hard to detect wanted differences or just plain text format.
>
> can be nice to have the first invisible row with some information about
> used formatting. pspg does some heuristic but this code is not nice and it
> is fragile.

I like pspg and use it myself, but I don't think a tool that does the
right thing by hiding a full screen of ---- from the user should
hinder making the same progress in psql with a simple pager.

Christoph

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2022-08-30 14:49:57 Re: \pset xheader_width page as default? (Re: very long record lines in expanded psql output)
Previous Message Jonathan S. Katz 2022-08-30 14:33:45 Re: SQL/JSON features for v15