| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgbench - implement strict TPC-B benchmark |
| Date: | 2019-08-01 06:57:13 |
| Message-ID: | alpine.DEB.2.21.1908010854050.2692@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> According to TPC themselves, "In contrast to TPC-A, TPC-B is not an
> OLTP benchmark. Rather, TPC-B can be looked at as a database stress
> test..." [1]. Sounds like classic pgbench to me.
>
> Not sure where that leaves this patch. What problem is it actually
> trying to solve?
That there is no builtin illustration of pgbench script features that
allow more realistic benchmarking.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2019-08-01 07:00:41 | Re: refactoring - share str2*int64 functions |
| Previous Message | Fabien COELHO | 2019-08-01 06:52:52 | Re: pgbench - implement strict TPC-B benchmark |