On Thu, Aug 17, 2006 at 12:51:24PM +0200, fgudin wrote:
> I found a few (different) references to that parameter on the
> web, but
> either ways (through DBD::Pg or with psql) fail:
> SET client_min_messages = WARNING;
> yields "ERROR: 'client_min_messages' is not a valid option name"
>
> I've g
Date: Thu, 17 Aug 2006 12:48:56 +0200
From: Francis GUDIN <[EMAIL PROTECTED]>
To: Martijn van Oosterhout
Cc: John Purser <[EMAIL PROTECTED]>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] VACUUM VERBOSE output to STDERR
Message-ID: <[EMAIL PROTECTED]>
In-Reply-To:
On Fri, Aug 11, 2006 at 06:10:48PM +0200, Francis GUDIN wrote:
> On Fri, 11 Aug 2006 08:05:44 -0700
> John Purser <[EMAIL PROTECTED]> 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
On Fri, 11 Aug 2006 08:05:44 -0700
John Purser <[EMAIL PROTECTED]> 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 fi
On Fri, 11 Aug 2006 15:49:56 +0200
Francis GUDIN <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm trying to solve a little issue: I wish to redirect my cron
> jobs'output to log files. STDOUT redirection is done inside the
> crontab, but VACUUM still yields its messages[1] through, onto
> STDERR, I gu
Hello,
I'm trying to solve a little issue: I wish to redirect my cron
jobs'output to log files. STDOUT redirection is done inside the crontab,
but VACUUM still yields its messages[1] through, onto STDERR, I guess.
I wouldn't like to '2>&1' also: I wish I could keep STDERR (what if an
error conditi
