Christopher Browne wrote:
> Jeff Frost <jeff at frostconsultingllc.com> writes:
>   =

>> 			   And that's different from log_level in slon.conf?=C2  Here's the c=
omment from the sample:
>> 				 # Debug log level (higher value =3D=3D> more output).=C2  Range: [0=
,4], default 4
>> 								log_level =3D 1
>> 	  That used to do the trick, but in 2.x it seems to be more chatty.=C2 =
 I tried setting it to 0 but it's still just as chatty.
>>     =

>
> I tried to make 2.x "more usefully chatty."
>
> It used to be that to get *anything* out of the logs, you'd have to
> tune them up to the "whoah, that's way too much!" level.
>
>   =

I'd definitely agree with that!
> I tried pushing stuff I thought was "boring" down towards debugging
> levels.
>
> It's possible that there's too much stuff at SLON_INFO level.
>
> It's pretty easy to grep for it all:
>
> for type in FATAL ERROR WARN CONFIG INFO DEBUG1 DEBUG2 DEBUG3 DEBUG4; do
>    find src/slon -name "*.c" | xargs grep -n "SLON_${type}" > /tmp/MSG_${=
type}
> done
>
>   =

How do the various types above map to the 0-4 log_level?

I'm looking here: http://slony.info/documentation/slon.html but it's
still not obvious to me which ones are which. I'm guessing up to info is
0 and 1-4 maps to debug1-4?
> I'd certainly be open to the suggestion that some logging messages
> ought to have their levels changed.
>
> I point out how to get the "grand list" to encourage thinking about it
> at least a little bit systematically.
>
> It seems fairly clear that the messages you mentioned are ones that
> warrant being moved to DEBUG1, so I'll do that, for sure.  If you have
> other suggestions, then suggest away.
>   =


-- =

Jeff Frost, Owner 	<jeff at frostconsultingllc.com>
Frost Consulting, LLC 	http://www.frostconsultingllc.com/
Phone: 916-647-6411	FAX: 916-405-4032

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20090728/=
ff758dbe/attachment.htm