| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Ants Aasma <ants(at)cybertec(dot)at>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Patch: add timing of buffer I/O requests |
| Date: | 2012-04-10 17:35:02 |
| Message-ID: | CA+TgmoYcLxQAzsYSZd3D1fwTMhhy+3FNr1MCF9vHKiOSCEwW4A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 10, 2012 at 12:11 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> No matter what we end up doing here it will be consistent with
>> something; I am reminded of the phrase "the good thing about standards
>> is that there are so many to choose from...".
>
> Well, FWIW I vote for making the new columns be float8 msec. If you
> don't want to change total_time to match, I guess there's no law that
> says it *has* to be consistent ...
Ugh. So the three ways of doing timing that we have already aren't
enough, and we need a fourth one? Ack!
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-04-10 17:38:36 | Re: psql: tab completions for 'WITH' |
| Previous Message | Robert Haas | 2012-04-10 17:33:26 | Re: Last gasp |