From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) |
Date: | 2014-06-03 20:18:14 |
Message-ID: | CA+TgmoYyqPLQQPf3D1Fu-fHL=WR0HEVjMLEJ_r7jqSXN4+2+FQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 3, 2014 at 4:02 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Andres Freund wrote:
>> On June 3, 2014 9:40:27 PM CEST, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>> >Maybe we could make it be controlled by TIMING. Seems like it fits
>> >well-enough there.
>>
>> Don't think that fits well - TIMING imo is about reducing the timing
>> overhead. But the server side total time is still interesting. I only
>> thought about tacking it onto COST because that already is pretty much
>> tailored for regression test usage. C.F. disabling the planning time.
>
> Pah. So what we need is a new mode, REGRESSTEST ON or something.
Well, we could invent that. But I personally think piggybacking on
COSTS makes more sense.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-06-03 20:24:58 | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) |
Previous Message | Alvaro Herrera | 2014-06-03 20:02:18 | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) |