pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tristan Partin <tristan@neon.tech>
To: Gurjeet Singh <gurjeet@singh.im>
To: Gregory Smith <gregsmithpgsql@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Use COPY for populating all pgbench tables
Date: Fri, 09 Jun 2023 12:58:31 -0500
Message-ID: <CT8BC7RXT33R.3CHYIXGD5NVHK@gonk> (raw)
In-Reply-To: <CABwTF4XMdHTxemhskad41Vj_hp2nPgifjwegOqR52_8-wEbv2Q@mail.gmail.com>
References: <CSTU5P82ONZ1.19XFUGHMXHBRY@c3po>
	<CAHLJuCW4gapAYZMc2vuy9mL2jdhNj3SLL9ef9U+stD=8EXfV=g@mail.gmail.com>
	<CABwTF4XMdHTxemhskad41Vj_hp2nPgifjwegOqR52_8-wEbv2Q@mail.gmail.com>

On Fri Jun 9, 2023 at 12:25 PM CDT, Gurjeet Singh wrote:
> On Fri, Jun 9, 2023 at 6:24 AM Gregory Smith <gregsmithpgsql@gmail.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

I think this would be nice to have if you wanted to submit a patch.

-- 
Tristan Partin
Neon (https://neon.tech)





view thread (31+ messages)  latest in thread

Message-ID: <CT8BC7RXT33R.3CHYIXGD5NVHK@gonk>
Permalink:  ../CT8BC7RXT33R.3CHYIXGD5NVHK@gonk/
Also on:    postgresql.org/message-id/CT8BC7RXT33R.3CHYIXGD5NVHK@gonk

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tristan@neon.tech, gurjeet@singh.im, gregsmithpgsql@gmail.com
  Subject: Re: Use COPY for populating all pgbench tables
  In-Reply-To: <CT8BC7RXT33R.3CHYIXGD5NVHK@gonk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox