Re: Unwanted debug messages

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: Joe Abbate <jma(at)freedomcircle(dot)com>
Cc: psycopg(at)postgresql(dot)org
Subject: Re: Unwanted debug messages
Date: 2013-08-06 23:30:55
Message-ID: 5201872F.50303@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

On 08/06/2013 09:10 AM, Joe Abbate wrote:
> Wences,
>
> On 06/08/13 10:35, Wenceslao Grillo wrote:
>> I don't think it's such an unusual setup: One box is running PostgreSQL
>> and my Python script is in another box, connecting to it (and getting
>> all the unwanted messages). Because right now I'm using a development
>> postgres box, I can log in to it and use psql but then I don't get those
>> messages. The messages show up on my screen, on my terminal when I run
>> my Python script. And I know that the debug messages are going to stderr
>> because if I say:
>> ./my_script.py 2>/dev/null
>> I get all the prints that I put in my code and none of the debug
>> messages. But I miss the messages from uncaught exceptions and the like,
>> that also go to stderr.
>
> I'm afraid there's still something different in your environment. I
> edited my postgresql.conf to change log_min_messages to debug3,
> restarted it and then ran the following:

The difference is you are working with log_min_messages which controls
what goes to the log file and Wenceslao is working with
client_min_messages which controls what goes to the client.

>
>
> Joe
>
>

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Browse psycopg by date

  From Date Subject
Next Message Tung Thanh 2013-08-13 14:22:55 psycopg with pg_filenode
Previous Message Wenceslao Grillo 2013-08-06 17:49:26 Re: Unwanted debug messages