Re: pgbench - extend initialization phase control

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: btendouan <btendouan(at)oss(dot)nttdata(dot)com>, "ibrar(dot)ahmad(at)gmail(dot)com:" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgbench - extend initialization phase control
Date: 2019-10-24 15:06:16
Message-ID: alpine.DEB.2.21.1910241658410.10865@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello,

>> Yep. Or anything else, including without (), to allow checking the
>> performance impact or non impact of transactions on the initialization
>> phase.
>
> Is there actually such performance impact? AFAIR most time-consuming part in
> initialization phase is the generation of pgbench_accounts data.

Maybe. If you cannot check, you can only guess. Probably it should be
small, but the current version does not allow to check whether it is so.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul Jungwirth 2019-10-24 15:17:23 Add json_object(text[], json[])?
Previous Message Surafel Temesgen 2019-10-24 14:54:33 Re: WIP: System Versioned Temporal Table