number of transactions actually processed: 301921
Just a thought before spending too much time on this subtle issue.
The patch worked reasonnably for 301900 transactions in your above run,
and the few last ones, less than the number of clients, show strange
latency figures which suggest that something is amiss in some corner case
when pgbench is stopping. However, the point of pgbench is to test a
steady state, not to achieve the cleanest stop at the end of a run.
So my question is: should this issue be a blocker wrt to the feature?
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: