Re: too much pgbench init output

Поиск
Список
Период
Сортировка
От Tomas Vondra
Тема Re: too much pgbench init output
Дата
Msg-id 50D22ADD.9070709@fuzzy.cz
обсуждение исходный текст
Ответ на Re: too much pgbench init output  (Jeevan Chalke <jeevan.chalke@enterprisedb.com>)
Ответы Re: too much pgbench init output
Re: too much pgbench init output
Список pgsql-hackers
On 19.12.2012 06:30, Jeevan Chalke wrote:
>
>
>
> On Mon, Dec 17, 2012 at 5:37 AM, Tomas Vondra <tv@fuzzy.cz
> <mailto:tv@fuzzy.cz>> wrote:
>
>     Hi,
>
>     attached is a new version of the patch that
>
>     (a) converts the 'log_step_seconds' variable to a constant (and does
>         not allow changing it using a command-line option etc.)
>
>     (b) keeps the current logging as a default
>
>     (c) adds a "-q" switch that enables the new logging with a 5-second
>         interval
>
>     I'm still not convinced there should be yet another know for tuning the
>     log interval - opinions?
>
>
> It seems that you have generated a patch over your earlier version and
> due to that it is not cleanly applying on fresh sources.
> Please generate patch on fresh sources.

Seems you're right - I've attached the proper patch against current master.

> However, I absolutely no issues with the design. Also code review is
> already done and looks good to me.
> I think to move forward on this we need someone from core-team. So I am
> planning to change its status to "ready-for-committor".
>
> Before that please provide updated patch for final code review.

thanks
Tomas

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Review of Row Level Security
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: system administration functions with hardcoded superuser checks