Re: Hide 'Execution time' in EXPLAIN (COSTS OFF)
От | Robert Haas |
---|---|
Тема | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) |
Дата | |
Msg-id | CA+TgmoYxaYoqeLXW=-eLhmabx7+jM0_AX9bynOZ+i5wLtuXbUg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Hide 'Execution time' in EXPLAIN (COSTS OFF) (David Rowley <dgrowleyml@gmail.com>) |
Ответы |
Re: Hide 'Execution time' in EXPLAIN (COSTS OFF)
|
Список | pgsql-hackers |
On Tue, Oct 14, 2014 at 3:03 AM, David Rowley <dgrowleyml@gmail.com> wrote: >> Andres Freund <andres@2ndquadrant.com> writes: >> > Well. Unless I miss something it doesn't resolve the problem that >> > started this thread. Namely that it's currently impossible to write >> > regression using EXPLAIN (ANALYZE, TIMING OFF. COSTS OFF). Which is >> > worthwhile because it allows to tests some behaviour that's only visible >> > in actually executed plans (like seing that a subtree wasn't executed). >> >> TBH, I don't particularly care about that. A new flag for turning >> "summary timing" off would answer the complaint with not too much >> non-orthogonality ... but I really don't find this use case compelling >> enough to justify adding a feature to EXPLAIN. >> > Hmm, was my case above not compelling enough? Apparently not to Tom, but it made sense to me. I think we should find a way to do something about this - maybe making TIMING OFF also suppress that info is the simplest approach. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: