> I have added the thread to the next CF (January 2018), and marked it as
> "ready for committer”.
That’s cool, thank you for review!
—
Thanks and Regards,
Alik Khilazhev
Postgres Professional:
http://www.postgrespro.com
The Russian Postgres Company
a
—
Thanks and Regards,
Alik Khilazhev
Postgres Professional:
http://www.postgrespro.com
The Russian Postgres Company
times" -> "once”.
I am not sure that it need to be fixed in this way, because there can be
another number instead of 1.
So, I updated it to “%d time(s)”
pgbench-zipf-10v.patch
Description: Binary data
—
Thanks and Regards,
Alik Khilazhev
Postgres Professional:
http://www.postgrespro.com
The Russian Postgres Company
sible warning
> message in the final report?
Also done. But one question: Should it be done by printing to stdout or stderr ?
> When/if the pgbench tap test patch get through, coverage tests should
> be added.
I have added few tests and I am not sure if they OK or not. It was my first
e
