From: | Gurjeet Singh <gurjeet(at)singh(dot)im> |
---|---|
To: | Gregory Smith <gregsmithpgsql(at)gmail(dot)com> |
Cc: | Tristan Partin <tristan(at)neon(dot)tech>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Use COPY for populating all pgbench tables |
Date: | 2023-06-09 17:25:14 |
Message-ID: | CABwTF4XMdHTxemhskad41Vj_hp2nPgifjwegOqR52_8-wEbv2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 9, 2023 at 6:24 AM Gregory Smith <gregsmithpgsql(at)gmail(dot)com> wrote:
>
> Unfortunately there's no simple command line option to change just that one thing about how pgbench runs. You have to construct a command line that documents each and every step you want instead. You probably just want this form:
>
> $ pgbench -i -I dtGvp -s 500
The steps are severely under-documented in pgbench --help output.
Grepping that output I could not find any explanation of these steps,
so I dug through the code and found them in runInitSteps(). Just as I
was thinking of writing a patch to remedy that, just to be sure, I
checked online docs and sure enough, they are well-documented under
pgbench [1].
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.
[1]: https://www.postgresql.org/docs/15/pgbench.html
Best regards,
Gurjeet
http://Gurje.et
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2023-06-09 17:45:27 | Re: win32ver data in meson-built postgres.exe |
Previous Message | Bruce Momjian | 2023-06-09 16:44:03 | Re: Partial aggregates pushdown |