| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | greg(at)2ndQuadrant(dot)com, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement) |
| Date: | 2013-07-18 09:53:38 |
| Message-ID: | alpine.DEB.2.02.1307181107220.3991@localhost6.localdomain6 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Tatsuo
> I think current measurement method will give enough confusion if it's
> not provided with detailed explanation. Could you please provide doc
> updatation?
Please find a v17 proposition with an updated and extended documentation,
focussed on clarifying the lag measure and its implications, and taking
into account the recent discussion on the list with you & Greg.
However I'm not a native English speaker, if you find that some part are
not clear enough, please tell me what can be improved further.
--
Fabien.
| Attachment | Content-Type | Size |
|---|---|---|
| pgbench-throttle-v17.patch | text/x-diff | 13.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2013-07-18 10:21:00 | Re: Add visibility map information to pg_freespace. |
| Previous Message | Tatsuo Ishii | 2013-07-18 08:42:37 | Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement) |