Re: VACUUM VERBOSE output to STDERR

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Francis GUDIN <fgudin(at)cri74(dot)org>
Cc: John Purser <jmpurser(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: VACUUM VERBOSE output to STDERR
Date: 2006-08-11 16:51:24
Message-ID: 20060811165124.GC950@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Aug 11, 2006 at 06:10:48PM +0200, Francis GUDIN wrote:
> On Fri, 11 Aug 2006 08:05:44 -0700
> John Purser <jmpurser(at)gmail(dot)com> wrote:
>
> > Take a look at the "tee" command that takes stdin and writes it to
> > stdout AND a file. If I understand you correctly you DO want to keep
> > stdout and stderr as two separate streams, write (at least) std err to
> > a log file, but have the error messages e-mailed to you as part of
> > your cron job. <snip>
>
> Thanks for your suggestion, but my concern is more about vacuum's
> behaviour, in fact:
> those messages are purely /informative/ and get sent to STDERR.
> This seems wrong to me: 'mundane' activity should be output to STDOUT and
> 'exceptional conditions' deserve the special fd, don't they ?

Well, I don't think psql or libpq really distinguishes them that much.
Normally you just set client_min_messages to suppress the messages you
don't want.

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-08-11 16:58:24 Re: Add column
Previous Message Joshua D. Drake 2006-08-11 16:40:56 Re: Tuning to speed select