On Wed, Dec 14, 2011 at 4:45 AM, Magnus Hagander <mag...@hagander.net> wrote:
>>> * There are a number of things that are always written to stdout, that
>>> there is no way to redirect. In some cases it's interactive prompts -
>>> makes sense - but also for example the output of \timing goes to
>>> stdout always. Is there some specific logic behind what/when this
>>> should be done?
>> Everything that is not an error goes to stdout, no?  Except the query
>> output, if you change it.
>> Maybe the way to do what you want is to invent a new setting that
>> temporarily changes stdout.
> Yeah, that might be it. Or I need separate settings for "put errors in
> the query output stream" and "put non-query-output-but-also-non-errors
> in the query output stream". The effect would be the same, I guess...

That seems an awful lot harder (and messier) than just changing the
all the call sites to use the same error-reporting function.

Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to