| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Jan Wieck <wieck(at)debis(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Anyone for prettyprinted EXPLAIN VERBOSE? |
| Date: | 1999-12-18 21:57:27 |
| Message-ID: | 1461.945554247@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Actually, something unrelated (must have been the notices popping up in
> the regression tests) led me to the idea of redirecting notice output into
> the regular query output channel in psql, which would make it subject to
> the pager if you have one set up. That would help those complaining about
> 100s of lines coming down their terminal. On my todo list.
This may be a bad idea. There are many people who use psql in shell
scripts, and for them it is critical that non-data messages like NOTICEs
get sent to stderr, *not* mixed in with query results on stdout.
If you can arrange to page stderr output, cool...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-12-18 22:14:07 | Re: pgindent (Re: [HACKERS] LONG varsize - how to go on) |
| Previous Message | Vince Vielhaber | 1999-12-18 21:44:39 | Re: pgindent (Re: [HACKERS] LONG varsize - how to go on)t |