Re: Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY)

From: Boris Mironov <boris_mironov(at)outlook(dot)com>
To: Hannu Krosing <hannuk(at)google(dot)com>, solai v <solai(dot)cdac(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Madyshev Egor <E(dot)Madyshev(at)ftdata(dot)ru>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Subject: Re: Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY)
Date: 2026-10-13 12:17:36
Message-ID: PH0PR08MB70206101FCD0736F03B79F4A889E2@PH0PR08MB7020.namprd08.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Solai,

> Is the warning for multiple data-generation modes already covered by
> the existing regression tests?

This is just a warning since official version of the pgbench doesn't check
for multiple calls to init the dataset. The purpose of the warning is to
highlight that user requested multiple inits and last one will overwrite
results of all previous ones. Therefor IMHO there is no need to create
special tests to cover presence of this warning.

> Based on my testing, the patch works as expected for the tested scenario.

Thank you very much for taking time to test this patch.

Regards,
solai

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2026-10-13 12:42:51 Re: pgsql: Don't trust NOT NULL on virtual generated columns of partitioned
Previous Message Zhijie Hou 2026-10-13 12:16:33 Re: Fix WITHOUT OVERLAPS multirange with location replication