From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Gerdan Santos <gerdan(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: \timing interval |
Date: | 2016-09-06 18:45:47 |
Message-ID: | 8925.1473187547@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Corey Huinker <corey(dot)huinker(at)gmail(dot)com> writes:
> On Sun, Sep 4, 2016 at 7:05 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>> 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.
If we like this specific output format, I'd be inclined to just
copy-and-paste the code from psql. I seriously doubt that getting type
interval involved in the discussion would lead to a shorter or
better-performing solution.
> 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.
Ugh. There are multiple ways to get that already, and it's not like
space in EXPLAIN's output is not a precious resource.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2016-09-06 18:51:14 | Re: Vacuum: allow usage of more than 1GB of work mem |
Previous Message | Pavel Stehule | 2016-09-06 18:44:54 | Re: Showing parallel status in \df+ |