| From: | Francis GUDIN <fgudin(at)cri74(dot)org> |
|---|---|
| To: | John Purser <jmpurser(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: VACUUM VERBOSE output to STDERR |
| Date: | 2006-08-11 16:10:48 |
| Message-ID: | 20060811181048.435f2076@pc07.cri.cur-archamps.fr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 ?
Francis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. O'Connor | 2006-08-11 16:21:16 | Re: How to use the full text index feature on PostgreSQL |
| Previous Message | Michael Meskes | 2006-08-11 16:09:16 | Re: Connection string |