Re: EXPLAIN ANALYZE

Поиск
Список
Период
Сортировка
От Jim C. Nasby
Тема Re: EXPLAIN ANALYZE
Дата
Msg-id 20061213194646.GL6551@nasby.net
обсуждение исходный текст
Ответ на Re: EXPLAIN ANALYZE  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: EXPLAIN ANALYZE  (Joshua Reich <josh@root.net>)
Список pgsql-hackers
On Mon, Dec 11, 2006 at 12:24:12AM +0100, Peter Eisentraut wrote:
> Simon Riggs wrote:
> > Well, I'd like a way of making EXPLAIN ANALYZE return something
> > useful within a reasonable amount of time. We can define that as the
> > amount of time that the user considers is their goal for the query.
> 
> What sort of "useful" results would you expect to be able to see from 
> such an aborted EXPLAIN ANALYZE?  I cannot quite imagine what 
> instructive value a partially executed plan output would have.  It's 
> not like we can somehow ensure executing an equal proportion of each 
> plan node or something.  Do you have a specific case in mind?

The query is most likely to get canceled while it is working on whatever
node in the plan is the bottleneck, and it's likely going to be easy to
spot since nodes above it wouldn't have gotten much done.
-- 
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Simon Riggs"
Дата:
Сообщение: pg_standby and build farm
Следующее
От: "Simon Riggs"
Дата:
Сообщение: Re: recovery.conf parsing problems