From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Getting rid of extra gettimeofday() calls |
Date: | 2006-06-19 17:45:13 |
Message-ID: | 20060619174513.GX93655@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 19, 2006 at 11:17:48AM -0400, Tom Lane wrote:
> instead? The effect would be that for an idle backend,
> pg_stat_activity.query_start would reflect the start time of its latest
> query instead of the time at which it finished the query. I can see
> some use for the current behavior but I don't really think it's worth
> the overhead of a gettimeofday() call.
Perhaps make it a compile-time option... I suspect that there's people
making use of that info in their monitoring tools. Though, those people
are probably also likely to have log_duration=true, so maybe the same
trick of gettimeofday() once at statement end and copying it as needed
would work.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2006-06-19 19:04:39 | Re: sync_file_range() |
Previous Message | Florian Weimer | 2006-06-19 16:47:00 | Re: sync_file_range() |