From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gerdan Santos <gerdan(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: \timing interval |
Date: | 2016-09-06 18:40:06 |
Message-ID: | CADkLM=cdyWdRAsQy3+87-H3pwQ052h-LMQD4rDzNTsZXMrdSYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Sep 4, 2016 at 7:05 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> On 9/3/16 2:35 PM, Tom Lane wrote:
>
>> I pushed the patch using this:
>>
>> Time: 176460001.200 ms (2 d 01:01:00.001)
>>
>> and all else as before.
>>
>
> I'd find this useful in the final output of EXPLAIN ANALYZE as well; any
> objections to adding it?
It's sorta out of my hands now, but what Tom said earlier is that because
this is client-side code, it wouldn't use existing interval code.
EXPLAIN *is* server-side, we couldn't use this code, but we could leverage
existing interval code there to achieve a similar concept.
I have another thing I'd like to add to EXPLAIN output : server version
number output. So maybe we can pick those up in another thread.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2016-09-06 18:44:54 | Re: Showing parallel status in \df+ |
Previous Message | Tom Lane | 2016-09-06 18:30:27 | Re: [PATCH] Alter or rename enum value |