|From:||Tomas Vondra <tv(at)fuzzy(dot)cz>|
|Subject:||Re: PATCH: pgbench - aggregation of info written into log|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 3.9.2012 01:28, Jeff Janes wrote:
> On Sun, Sep 2, 2012 at 3:46 PM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:
>> Fixed. I've kept use_log_agg only and I've removed the default. Also
>> I've added one more check (that the total duration is a multiple of
>> the aggregation interval).
> Hi Tomas,
> In the docs, -l is an option, not an application:
> Also, the docs still refer to <option>-A</option>, rather than to
> <option>--aggregate-interval</option>, in a few places.
> I think a section in the docs that points out that transactions run by
> specifying mulitple -f will be mingled together into an interval would
> be a good idea, as that could easily be overlooked (as I did earlier).
Fixed, added a paragraph mentioning this.
> The docs do not mention anywhere what the units for the latencies are.
> I think the format of the logfile should somehow make it unmistakably
> different from the regular -l logfile, for example by prefixing every
> line with "Aggregate: ". Or maybe there is some other solution, but
> I think that having two log formats, both of which consist of nothing
> but 6 integers, but yet mean very different things, is a recipe for
Not sure how to do that, I'd say it's a responsibility of the user.
> Is it unavoidable that the interval be an integral number of seconds?
> I found the units in the original code confusing, so maybe there is
> some reason it needs to be like that that I don't understand yet.
> I'll look into it some more.
Not really, but I don't see a real use case for such intervals, so I'm
keeping the integers for now.
Also, I've realized the last interval may not be logged at all - I'll
take a look into this in the next version of the patch.
|Next Message||Kevin Grittner||2012-09-20 21:05:19||Assigning NULL to a record variable|
|Previous Message||Tom Lane||2012-09-20 20:34:02||Re: Re: proposal and patch : support INSERT INTO...RETURNING with partitioned table using rule|