From: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: too much pgbench init output |
Date: | 2012-12-19 21:00:13 |
Message-ID: | 50D22ADD.9070709@fuzzy.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 19.12.2012 06:30, Jeevan Chalke wrote:
>
>
>
> On Mon, Dec 17, 2012 at 5:37 AM, Tomas Vondra <tv(at)fuzzy(dot)cz
> <mailto:tv(at)fuzzy(dot)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
Attachment | Content-Type | Size |
---|---|---|
pgbench-logging-v5.patch | text/plain | 3.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2012-12-19 21:02:11 | Re: system administration functions with hardcoded superuser checks |
Previous Message | Simon Riggs | 2012-12-19 20:55:19 | Re: Review of Row Level Security |