On Sun, Nov 20, 2011 at 4:27 AM, Tatsuo Ishii <is...@sraoss.co.jp> wrote: >>>> By enabling "log_connections" you have your client IP and pgpool child >>>> pid in your log. Since the log for "unable parse..." includes pgpool >>>> child pid, you can get client IP by checking pgpool child pid. >>>> >>>> LOG: pid 4327: connection received: host=[local] >>>> LOG: pid 4327: SimpleQuery: Unable to parse the query: select select; >>> >>> I was hoping there was some way other than enabling log_connections, >>> as that's going to log every single connection (millions/day), even if >>> there's no error? >> >> Good suggestion. I would like to include it for next release (3.2) >> unless someone beats me. > > Here is the patch I promised. Here are sample log entries. > > From TCP/IP client case: > 2011-11-20 21:15:52 LOG: pid 23045: SimpleQuery: Unable to parse the query: > "select select;" from client 127.0.0.1(33737) > > From Unix domain socket client case: > 2011-11-20 21:14:46 LOG: pid 23045: SimpleQuery: Unable to parse the query: > "select select;" from local client
The sample log entries look good to me, thanks! _______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
