From: | Gregory Smith <gregsmithpgsql(at)gmail(dot)com> |
---|---|
To: | Gurjeet Singh <gurjeet(at)singh(dot)im> |
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-10 00:41:50 |
Message-ID: | CAHLJuCUp5_VUo+RJ+pSnxeiiZfcstRtTubRP8+u8NEqmrbp4aw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 9, 2023 at 1:25 PM Gurjeet Singh <gurjeet(at)singh(dot)im> wrote:
> > $ pgbench -i -I dtGvp -s 500
>
> The steps are severely under-documented in pgbench --help output.
>
I agree it's not easy to find information. I just went through double
checking I had the order recently enough to remember what I did. The man
pages have this:
> Each step is invoked in the specified order. The default is dtgvp.
Which was what I wanted to read. Meanwhile the --help output says:
> -I, --init-steps=[dtgGvpf]+ (default "dtgvp")
%T$%%Which has the information without a lot of context for what it's used
for. I'd welcome some text expansion that added a minimal but functional
improvement to that the existing help output; I don't have such text.
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2023-06-10 00:49:00 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
Previous Message | Jeff Davis | 2023-06-10 00:37:57 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |