From: | Greg Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: generic options for explain |
Date: | 2009-05-27 11:44:06 |
Message-ID: | 4136ffa0905270444o7c478b9dh98f057da8c43fc90@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 27, 2009 at 1:30 AM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> The big plus of the current technique is that it is so convenient to
> Ctrl+C something which is running too long, arrow up, hit Home, and
> put the EXPLAIN word in front. Turning the query into a character
> string literal and feeding it to a function would be a big step
> backward.
>
> A big down side of the current technique is that you can't get both
> the results of a SELECT and its plan. I haven't seen any discussion
> here about emitting the EXPLAIN output through some INFO messages or
> some such, and letting the query return its normal results, but I feel
> that would be a significant improvement, if it that be done.
Would something like this address both of your issues?
http://article.gmane.org/gmane.comp.db.postgresql.devel.patches/21614/match=siginfo
It let you hit a control character while the query was running to view
the explain analyze for the results so far. The query kept running and
you could request further updates whenever you wanted.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-05-27 12:04:34 | replace plpgsql_dstring by StringInfo |
Previous Message | Markus Wanner | 2009-05-27 11:36:25 | Re: PostgreSQL Developer meeting minutes up |