psql: Fix \pset by adding missed xheader_width option to the help

Started by Pavel Luzanovover 1 year ago3 messageshackers
Jump to latest
#1Pavel Luzanov
p.luzanov@postgrespro.ru

I found that the help for \pset command missed xheader_width option.
Please, consider this small correction.

--
Pavel Luzanov
Postgres Professional:https://postgrespro.com

Attachments:

v1-0001-psql-Fix-help-for-pset-by-adding-missed-xheader_w.patchtext/x-patch; charset=UTF-8; name=v1-0001-psql-Fix-help-for-pset-by-adding-missed-xheader_w.patchDownload+5-3
#2Michael Paquier
michael@paquier.xyz
In reply to: Pavel Luzanov (#1)
Re: psql: Fix \pset by adding missed xheader_width option to the help

On Thu, Nov 21, 2024 at 10:50:41PM +0300, Pavel Luzanov wrote:

I found that the help for \pset command missed xheader_width option.
Please, consider this small correction.

Good catch. This is a mistake from a45388d6e098. The patch should
have used HELP0() as this is a single variable, and the listing of
values uses squared parenthesis.

I've noticed that \parse is listed in an incorrect section, while
double-checking the whole. I'll also fix while on it, the second one
is on me.
--
Michael

#3Pavel Luzanov
p.luzanov@postgrespro.ru
In reply to: Michael Paquier (#2)
Re: psql: Fix \pset by adding missed xheader_width option to the help

On 22.11.2024 05:52, Michael Paquier wrote:

On Thu, Nov 21, 2024 at 10:50:41PM +0300, Pavel Luzanov wrote:

I found that the help for \pset command missed xheader_width option.

Good catch. This is a mistake from a45388d6e098. The patch should
have used HELP0() as this is a single variable, and the listing of
values uses squared parenthesis.

Of course, you are right. It's my inattention.

I've noticed that \parse is listed in an incorrect section, while
double-checking the whole. I'll also fix while on it, the second one
is on me.

I see your commits 768dfd8e6 and ea1581692.
Thank you vary much.

--
Pavel Luzanov
Postgres Professional:https://postgrespro.com