Re: Rationalizing EXPLAIN VERBOSE output

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(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 04:43:19
Message-ID: 13303.1015821799@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> ... I am concerned that making explain like
> SELECT means it is on the one piece of debug info you can't get into the
> server logs. Query dump can already get into the query logs, but not
> EXPLAIN non-verbose.

A week ago you were willing to set things up so that INFO output could
not get into the server logs period. Why so concerned now? EXPLAIN
output does not seem like suitable data for logs to me, any more than
the output of SELECT queries does. It's only a historical artifact
that we are accustomed to thinking of it as being loggable.

> In fact, as Peter explains it, NOTICE \g goes to the terminal because it
> is assumed to be an error. Maybe we need to make psql smarter and only
> send ERROR/WARNING to terminal, and INFO/NOTICE to the log file.

While I suggested that to start with, it seems like a bad idea on
further thought. Mixing INFO/NOTICE with query output would be just
like piping stdout and stderr to the same place. There's usually
good reason to keep them separate.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-03-11 04:45:18 Re: Rationalizing EXPLAIN VERBOSE output
Previous Message Bruce Momjian 2002-03-11 04:36:05 Re: Rationalizing EXPLAIN VERBOSE output