Thread
Commits
-
psql: Fix category of \parse in output of --help=commands and \?
- ea15816928c1 18.0 landed
-
psql: Include \pset xheader_width in --help=commands|variables
- 4ecb136bfaa7 16.7 landed
- e6d6f2e46b57 17.3 landed
- 768dfd8e6575 18.0 landed
-
psql: Fix \pset by adding missed xheader_width option to the help
Pavel Luzanov <p.luzanov@postgrespro.ru> — 2024-11-21T19:50:41Z
I found that the help for \pset command missed xheader_width option. Please, consider this small correction. -- Pavel Luzanov Postgres Professional:https://postgrespro.com
-
Re: psql: Fix \pset by adding missed xheader_width option to the help
Michael Paquier <michael@paquier.xyz> — 2024-11-22T02:52:40Z
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
-
Re: psql: Fix \pset by adding missed xheader_width option to the help
Pavel Luzanov <p.luzanov@postgrespro.ru> — 2024-11-22T13:53:32Z
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