From: Andreas Joseph Krogh <andreak@officenet.no>
Organization: OfficeNet AS
To: pgsql-sql@postgresql.org, Tony Wasson <ajwasson@gmail.com>
Subject: Re: echo/printf function in plpgsql
Date: Tue, 19 Jul 2005 22:36:48 +0200
User-Agent: KMail/1.7.2
References: <200507191651.28648.andreak@officenet.no>
	<200507191758.05273.andreak@officenet.no>
	<6d8daee30507191309515f33c4@mail.gmail.com>
In-Reply-To: <6d8daee30507191309515f33c4@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200507192236.48641.andreak@officenet.no>

On Tuesday 19 July 2005 22:09, Tony Wasson wrote:
> On 7/19/05, Andreas Joseph Krogh <andreak@officenet.no> wrote:
> > On Tuesday 19 July 2005 17:18, Richard Huxton wrote:
> > > Andreas Joseph Krogh wrote:
> > > > Hi all!
> > > >
> > > > Is there a way of echo'ing a string(like "raise notice 'this is id%',
> > > > id") from plpgsql? I want to echo/print it to STDOUT 'cause the
> > > > notice-mechanism produces too much noise IMH.
> > >
> > > Your function is running in the backend. You don't have a STDOUT
> > > (although you might have redirected STDERR for logging).
> >
> > I see. Can I make the ouput somehow less verbose? It spits out a lot of
> > noise for each "NOTICE":
>
> You can control the severity messages sent to your client by first
> setting client_min_message.
>
> Try SET client_min_messages = WARNING;

Thanks

--
AJK