From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Rationalizing EXPLAIN VERBOSE output |
Date: | 2002-03-11 02:33:37 |
Message-ID: | 200203110233.g2B2Xbh12367@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Tom Lane writes:
> >> ... How hard would it be to get psql to
> >> send notice output into a \g file?
>
> > \g (and \o) send only the query results to a file. The idea is that you
> > want to save the results, but if there's a warning or error, you want to
> > see it. We could add alternative commands (\G and \O?) that save the
> > notices and errors as well. Not sure if this is useful beyond this
> > application. In non-interactive situations you'd usually use shell
> > redirections to save all output.
>
> The other possibility is to make EXPLAIN output look like a SELECT
> result. Not sure how hard this would be to do, but in the long run
> I suppose that would be the direction to move in.
Seems EXPLAIN as SELECT would break our elog() control of output to the
server logs.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-03-11 02:36:16 | Re: Rationalizing EXPLAIN VERBOSE output |
Previous Message | Bruce Momjian | 2002-03-11 02:32:03 | Re: Rationalizing EXPLAIN VERBOSE output |