From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
---|---|
To: | jgdr(at)dalibo(dot)com |
Cc: | thomas(dot)munro(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Retry in pgbench |
Date: | 2021-04-16 13:15:08 |
Message-ID: | 20210416.221508.2164490604091193327.t-ishii@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> This usecase is not about benchmarking. It's about generating constant trafic
> to be able to practice/train some [auto]switchover procedures while being close
> to production activity.
>
> In this contexte, a max-saturated TPS of one node is not relevant. But being
> able to add some stats about downtime might be a good addition.
Oh I see. That makes sense.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Esteban Zimanyi | 2021-04-16 13:34:32 | Error when defining a set returning function |
Previous Message | Jehan-Guillaume de Rorthais | 2021-04-16 13:09:36 | Re: Retry in pgbench |