Re: Patch to show individual statement latencies in pgbench output

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Florian Pflug <fgp(at)phlo(dot)org>, PostgreSQL-development hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch to show individual statement latencies in pgbench output
Date: 2010-08-13 00:22:18
Message-ID: 4C64903A.4000405@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> It could be fixed with enough effort, by having the child threads pass
> back their numbers through the child-to-parent pipes. I'm not
> interested in doing that myself though.
>

That does seem an improvement with a very limited user base it's
applicable to. Probably the next useful improvement to this feature is
to get per-statement data into the latency log files if requested. If
this issue gets in the way there somehow, maybe it's worth squashing
then. I don't think it will though.

--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-08-13 01:24:50 Re: RecordTransactionCommit() and SharedInvalidationMessages
Previous Message Robert Haas 2010-08-12 23:49:08 Re: including backend ID in relpath of temp rels - updated patch