Re: Use COPY for populating all pgbench tables

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-10 03:52:29
Message-ID: CABwTF4Ww42arY1Q88_iaraVLxqSU+8Yb4oKiTT5gD1sineog9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 9, 2023 at 6:20 PM Gurjeet Singh <gurjeet(at)singh(dot)im> wrote:
> On Fri, Jun 9, 2023 at 5:42 PM Gregory Smith <gregsmithpgsql(at)gmail(dot)com> wrote:
> > 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.
>
> Please see attached 2 variants of the patch. Variant 1 simply tells
> the reader to consult pgbench documentation. The second variant
> provides a description for each of the letters, as the documentation
> does. The committer can pick the one they find suitable.

(I was short on time, so had to keep it short in the above email. To
justify this additional email, I have added 2 more options to choose
from. :)

The text ", in the specified order" is an important detail, that
should be included irrespective of the rest of the patch.

My preference would be to use the first variant, since the second one
feels too wordy for --help output. I believe we'll have to choose
between these two; the alternatives will not make anyone happy.

These two variants show the two extremes; bare minimum vs. everything
but the kitchen sink. So one may feel the need to find a middle ground
and provide a "sufficient, but not too much" variant. I have attempted
that in variants 3 and 4; see attached.

The third variant does away with the list of steps, and uses a
paragraph to describe the letters. And the fourth variant makes that
paragraph terse.

In the order of preference I'd choose variant 1, then 2. Variants 3
and 4 feel like a significant degradation from variant 2.

Attached samples.txt shows the snippets of --help output of each of
the variants/patches, for comparison.

Best regards,
Gurjeet
http://Gurje.et

Attachment Content-Type Size
samples.txt text/plain 2.4 KB
variant-1-brief-pointer-to-docs.patch application/x-patch 860 bytes
variant-2-detailed-description.patch application/x-patch 1.3 KB
variant-3-details-not-list.patch application/x-patch 1.2 KB
variant-4-terse-details-not-list.patch application/x-patch 1.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-06-10 04:00:05 Re: Documentation for building with meson
Previous Message Andres Freund 2023-06-10 03:16:33 Re: [PATCH] Missing dep on Catalog.pm in meson rules