| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: EXPLAIN ANALYZE |
| Date: | 2006-12-10 23:24:12 |
| Message-ID: | 200612110024.13036.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2006-12-10 23:40:17 | Re: EXPLAIN ANALYZE |
| Previous Message | Simon Riggs | 2006-12-10 23:19:39 | Re: postgresql roadmap for horizontal scalability? |