Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q7gNo-0008Hv-KZ for pgsql-hackers@arkaria.postgresql.org; Fri, 09 Jun 2023 17:58:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q7gNn-0000yp-5b for pgsql-hackers@arkaria.postgresql.org; Fri, 09 Jun 2023 17:58:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q7gNm-0000yZ-O7 for pgsql-hackers@lists.postgresql.org; Fri, 09 Jun 2023 17:58:42 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q7gNf-001GCk-2V for pgsql-hackers@postgresql.org; Fri, 09 Jun 2023 17:58:41 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-19f7e8f8e3bso769121fac.3 for ; Fri, 09 Jun 2023 10:58:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neon-tech.20221208.gappssmtp.com; s=20221208; t=1686333513; x=1688925513; h=in-reply-to:references:message-id:from:to:subject:cc:date :content-transfer-encoding:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=uxLhl3DqK0veRPPnUkngAwWqRR77yTg0+m+RG4tt8Mo=; b=fTTCD6Umkq/A5r6SONFRdwlUrfFETGOe7quFD+J9kN9RGEs+5M+gzsdcu7FwDlzdH2 izQzRm2jpIUeR0QPX0oFWRPG31jtuFUmE815AWyYtAnIJ6SApMm2DaTl+IIR6IoFtEzU jrIfZTgP3y6NCrGD3e+wUN97gHI11TKsbxlCoPRrwifoYNjVe1WDlRKMi6LxKTIua9cc tVbpFCG9gm/dORYxGLSwoC1HHvFNyiPq0jkjgVNDqs9gNh087ri8Iv9HX4GZwxSF4SIA K8L0FGEsDnfaZtLc7vr9sTlLqO/Yf5rDJ/U4XdF9kxXrthHGJEXdEDC30HvIGTAmXBdJ LOrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686333513; x=1688925513; h=in-reply-to:references:message-id:from:to:subject:cc:date :content-transfer-encoding:mime-version:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=uxLhl3DqK0veRPPnUkngAwWqRR77yTg0+m+RG4tt8Mo=; b=KxtABv5Ye86Nsy9Keyd7xz2carIXw+o6XbjEeuLNbDCfyRwE3/uqtpMjqIB3z3/9Ag tH+XIcz0IoP0RpxIIH2C0nqJiJVcvlHdURf00QSMLshPUy9SY6QYEiB8p2UpOopwaSlv K4dcAQacCAfwBlxmJfHW4KIW2cIzjEdA1NlymzLpuQCS6/QemP6CAKm2ZSDjv6XdOxDj KBEHjcKY/6treCAPpwZwuTfaFpf3XIUQtEJVcMfQgJnDgU5uC4vrm003xH7RW3f4nMgb 80cqeFJt7Mt8W84WvL8nnDpthG8wlHK25+bdZ2rNFpx2/a4HVcr2JcXBlhteD900zz/c q1ww== X-Gm-Message-State: AC+VfDxDp3e6X0+YaSgSP2EQKvQV1LHQYCzkYOkwjVTq3VRu3s1TsEhz IwpinsGjfHB4FdhOePI4GZS2KA== X-Google-Smtp-Source: ACHHUZ4v9SiW08qox5I2icQwovs+uEFLiDKPd9s86YX3xz/ckYHAn5TZU0cUSwqmQSYkzeYmeUC3uA== X-Received: by 2002:a05:6871:6bb0:b0:19f:238e:dd87 with SMTP id zh48-20020a0568716bb000b0019f238edd87mr1550558oab.47.1686333513300; Fri, 09 Jun 2023 10:58:33 -0700 (PDT) Received: from localhost ([2607:fb90:e696:c1dc:3996:e070:71ee:42fb]) by smtp.gmail.com with ESMTPSA id p14-20020a056870a54e00b0017b21991355sm2466796oal.20.2023.06.09.10.58.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 09 Jun 2023 10:58:32 -0700 (PDT) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 09 Jun 2023 12:58:31 -0500 Cc: Subject: Re: Use COPY for populating all pgbench tables To: "Gurjeet Singh" , "Gregory Smith" From: "Tristan Partin" Message-Id: X-Mailer: aerc 0.15.2-33-gedd4752268b2 References: In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri Jun 9, 2023 at 12:25 PM CDT, Gurjeet Singh wrote: > On Fri, Jun 9, 2023 at 6:24=E2=80=AFAM Gregory Smith 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 th= at 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. --=20 Tristan Partin Neon (https://neon.tech)