Use COPY for populating all pgbench tables

Tristan Partin <tristan@neon.tech>

From: "Tristan Partin" <tristan@neon.tech>

To: <pgsql-hackers@postgresql.org>

Date: 2023-05-23T17:33:21Z

Lists: pgsql-hackers

Attachments

v1-0001-Move-constant-into-format-string.patch (text/x-patch) patch v1-0001
v1-0002-Use-COPY-instead-of-INSERT-for-populating-all-tab.patch (text/x-patch) patch v1-0002

Hello,

We (Neon) have noticed that pgbench can be quite slow to populate data
in regard to higher latency connections. Higher scale factors exacerbate
this problem. Some employees work on a different continent than the
databases they might be benchmarking. By moving pgbench to use COPY for
populating all tables, we can reduce some of the time pgbench takes for
this particular step. 

I wanted to come with benchmarks, but unfortunately I won't have them
until next month. I can follow-up in a future email.

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

Commits

pgbench: Use COPY for client-side data generation
- e35cc3b3f2d0 17.0 landed
pgbench: Add TAP tests to check consistency of data generated
- 29836df323d7 17.0 landed
pgbench: Move constant into format string
- 11f36694091c 17.0 landed