From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Gurjeet Singh <gurjeet(at)singh(dot)im> |
Cc: | Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Better help output for pgbench -I init_steps |
Date: | 2023-09-19 07:20:36 |
Message-ID: | a37abd83-001b-4324-d5bd-7ff0d037ef64@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12.07.23 15:41, Alvaro Herrera wrote:
> On 2023-Jul-12, Gurjeet Singh wrote:
>
>> The init-steps are severely under-documented in pgbench --help output.
>> I think at least a pointer to the the pgbench docs should be mentioned
>> in the pgbench --help output; an average user may not rush to read the
>> code to find the explanation, but a hint to where to find more details
>> about what the letters in --init-steps mean, would save them a lot of
>> time.
>
> Agreed.
>
> I would do it the way `pg_waldump --rmgr=list` or `psql
> --help=variables` are handled: they give you a list of what is
> supported. You don't have to put the list in the main --help output.
I think I prefer variant 2. Currently we only have 8 steps, so it might
be overkill to separate them out into a different option.
From | Date | Subject | |
---|---|---|---|
Next Message | Ryoga Yoshida | 2023-09-19 07:23:36 | Re: Bug fix for psql's meta-command \ev |
Previous Message | Peter Eisentraut | 2023-09-19 07:01:56 | Re: information_schema and not-null constraints |