Re: turning off notices - Mailing list pgsql-general

From Sue Fitt
Subject Re: turning off notices
Date
Msg-id 00d301c85ac0$4ad087a0$0200a8c0@wilfrid
Whole thread Raw
In response to turning off notices  ("Sue Fitt" <sfitt@fittconway.plus.com>)
List pgsql-general
Thanks, a combination of the two answers solves it:

echo 'set client_min_messages TO WARNING; SELECT * FROM show(1135311);' |
psql -d combilex

Notices and their context now gone. Not sure why I had to use ';' rather
than '\\' to join the two statements, but it's working so I'm happy.

Sue

----- Original Message -----
From: "Stephan Szabo" <sszabo@megazone.bigpanda.com>
To: "Sue Fitt" <sfitt@fittconway.plus.com>
Cc: <pgsql-general@postgresql.org>
Sent: Saturday, January 19, 2008 4:16 PM
Subject: Re: [GENERAL] turning off notices


> On Sat, 19 Jan 2008, Sue Fitt wrote:
>
>> Hi All,
>>
>> I'm having trouble with turning off notices. Within psql I use \set
>> VERBOSITY terse, which is fine. However, using psql -c I am having
>> trouble. It seems I should be able to use psql -qc 'mycommand' but I am
>> still getting notices output, e.g.
>>
>> psql -d combilex -qc 'SELECT * FROM show(1135311);'
>> NOTICE:  phonotactic error, please check transcription
>> CONTEXT:  SQL statement "SELECT etc....
>>
>> Is there a way to turn these notices off other than reconfiguring the
>> conf file and restarting the database? I am using 8.1.3.
>
> If you want no notices, you could try "set client_min_messages TO
> WARNING".
>
> --
> This email has been verified as Virus free.
> Virus Protection and more available at http://www.plus.net
>


pgsql-general by date:

Previous
From: Simon Riggs
Date:
Subject: Re: WARNINGs after starting backup server created with PITR
Next
From: Erik Jones
Date:
Subject: Re: WARNINGs after starting backup server created with PITR