Date: Thu, 17 Aug 2006 12:48:56 +0200
From: Francis GUDIN <[EMAIL PROTECTED]>
To: Martijn van Oosterhout <kleptog@svana.org>
Cc: John Purser <[EMAIL PROTECTED]>, pgsql-general@postgresql.org
Subject: Re: [GENERAL] VACUUM VERBOSE output to STDERR
Message-ID: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
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@svana.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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
