Search Postgresql Archives

Re: VACUUM VERBOSE output to STDERR

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Date: Thu, 17 Aug 2006 12:48:56 +0200
From: Francis GUDIN <fgudin@xxxxxxxxx>
To: Martijn van Oosterhout <kleptog@xxxxxxxxx>
Cc: John Purser <jmpurser@xxxxxxxxx>, pgsql-general@xxxxxxxxxxxxxx
Subject: Re: [GENERAL] VACUUM VERBOSE output to STDERR
Message-ID: <20060817124856.6bce4c9c@xxxxxxxxxxxxxxxxxxxxxxxx>
In-Reply-To: <20060811165124.GC950@xxxxxxxxx>
References: <20060811154956.5b04ddb3@xxxxxxxxxxxxxxxxxxxxxxxx>
	<20060811080544.c49c9499.jmpurser@xxxxxxxxx>
	<20060811181048.435f2076@xxxxxxxxxxxxxxxxxxxxxxxx>
	<20060811165124.GC950@xxxxxxxxx>
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@xxxxxxxxx> 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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux