Re: [PATCH] Reduce logging in dbpool_mysql.c

t; Alexander Malysh > > From: Stipe Tolj <st...@kannel.org> <mailto:st...@kannel.org> > Sent: Monday, September 26, 2016 07:35 PM > To: > Cc: kannel_dev_mailinglist <devel@kannel.org> <mailto:devel@kannel.org> > Subject: Re: [PATCH] Reduce loggin

Re: [PATCH] Reduce logging in dbpool_mysql.c

er 26, 2016 07:35 PM > *To*: > *Cc*: kannel_dev_mailinglist <devel@kannel.org> <devel@kannel.org> > *Subject*: Re: [PATCH] Reduce logging in dbpool_mysql.c > Am 24.09.2016 13:57, schrieb Rene Kluwen: > > I don’t agree completely with your reasoning. > > > > Ei

RE: [PATCH] Reduce logging in dbpool_mysql.c

ysh   From: Stipe Tolj <st...@kannel.org> Sent: Monday, September 26, 2016 07:35 PM To: Cc: kannel_dev_mailinglist <devel@kannel.org> Subject: Re: [PATCH] Reduce logging in dbpool_mysql.c Am 24.09.2016 13:57, schrieb Rene Kluwen: > I don’t agree completely with your reasoning. > &g

Re: [PATCH] Reduce logging in dbpool_mysql.c

Am 24.09.2016 13:57, schrieb Rene Kluwen: I don’t agree completely with your reasoning. Either you want debug information or you don’t. Enabling debug information yields a lot of information. What about if you want to debug the mysql pool usage? Still +0 from me in case it’s redundant info.

Re: [PATCH] Reduce logging in dbpool_mysql.c

I'm on your side but many Kannel users run in debug log level, and this particular information is the same every time - it doesn't change from request to request. It's a non essential patch just 'nice to have' for most. On Saturday, 24 September 2016, Rene Kluwen wrote: >

RE: [PATCH] Reduce logging in dbpool_mysql.c

I don’t agree completely with your reasoning. Either you want debug information or you don’t. Enabling debug information yields a lot of information. What about if you want to debug the mysql pool usage? Still +0 from me in case it’s redundant info. Van: devel