Re: PATCH: pgbench - break out timing data for initializationphases
От
Fabien COELHO
Тема
Re: PATCH: pgbench - break out timing data for initializationphases
Дата
Msg-id
alpine.DEB.2.20.1802220845100.3036@lancre
Ответ на
Список
Дерево обсуждения
PATCH: pgbench - break out timing data for initialization phases "Rady, Doug" <radydoug@amazon.com>
Re: PATCH: pgbench - break out timing data for initializationphases Fabien COELHO <coelho@cri.ensmp.fr>
Re: PATCH: pgbench - break out timing data for initialization phases "Rady, Doug" <radydoug@amazon.com>
Re: PATCH: pgbench - break out timing data for initialization phases Andres Freund <andres@anarazel.de>
Re: Re: PATCH: pgbench - break out timing data for initializationphases David Steele <david@pgmasters.net>
Re: PATCH: pgbench - break out timing data for initializationphases Fabien COELHO <coelho@cri.ensmp.fr>
Hello Doug, > Doing the "in progress" way suffers from everything before 'generating > data' possibly scrolling off the screen/window. Yeah, that is a point. I tend to "| less" when I want to see a long output in details, so it is not an issue for me. Also, I like to have an information when it is available, and not have to wait for the end. Finally, note that pre data loading operations are expected to be quite fast, thus not that significant (create table, ...). Longer operations would occur after a large data set is loaded, thus after the large loading progress output which scrolls the screen. > For me, it is much handier to look at one set of duration times all > reported together after all of the initialize phases are done. Then for this apporach the duration data must be stored and then printed in the end. -- Fabien.
В списке pgsql-hackers по дате отправления
От: Michael Paquier
Дата: