From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Jon <polandj(at)engin(dot)umich(dot)edu>, Justin Clift <justin(at)postgresql(dot)org>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: debug_level 0 does not stop debug messages |
Date: | 2001-05-08 20:13:44 |
Message-ID: | 7851.989352824@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> OK, I did a little research on this. It turns out that this code in
> vacuum.c:
> if (vacstmt->verbose)
> MESSAGE_LEVEL = NOTICE;
> else
> MESSAGE_LEVEL = DEBUG;
> controls whether the message comes out as a NOTICE or a DEBUG. My guess
> is that you are doing a VACUUM VERBOSE, and those are coming out in the
> server logs.
> Guys, is this the proper way to handle this?
It could probably be done better, but VACUUM has behaved like that for
quite a few years now. I don't see any need to change it until we have
a complete redesign of message handling in mind. Peter E. has muttered
about some ideas in that line...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-05-08 20:17:56 | New tests for new bugs (was Re: [BUGS] Re: backend dies on 7.1.1 loading large datamodel.) |
Previous Message | Bruce Momjian | 2001-05-08 18:28:30 | Re: debug_level 0 does not stop debug messages |