Re: VACUUM VERBOSE output to STDERR

Date: Thu, 17 Aug 2006 12:48:56 +0200
From: Francis GUDIN <fgudin(at)cri74(dot)org>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: John Purser <jmpurser(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] VACUUM VERBOSE output to STDERR
Message-ID: <20060817124856(dot)6bce4c9c(at)pc07(dot)cri(dot)cur-archamps(dot)fr>
In-Reply-To: <20060811165124(dot)GC950(at)svana(dot)org>
References: <20060811154956(dot)5b04ddb3(at)pc07(dot)cri(dot)cur-archamps(dot)fr>
<20060811080544(dot)c49c9499(dot)jmpurser(at)gmail(dot)com>
<20060811181048(dot)435f2076(at)pc07(dot)cri(dot)cur-archamps(dot)fr>
<20060811165124(dot)GC950(at)svana(dot)org>
Organization: Centre de Ressources Informatiques de Haute-Savoie
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

On Fri, 11 Aug 2006 18:51:24 +0200
Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
>
> 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.

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 got the feeling that it's a server-side global
configuration knob,
not accessible on a client by client basis, am I right ?

Francis