[pgpool-general: 974] Re: logging client source of errors

Tatsuo Ishii ishii at postgresql.org
Sat Sep 8 16:11:14 JST 2012

That requires new code because 3.2's new feature was added to know
which client sends stuid SQL. Maybe adding new switch like "log_client_ip"?
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> Greetings,
> I'm running 3.2.0.  One of the new features was that logged errors
> would report the client which triggered the error.  I do see that
> behavior under some circumstances, however not all the time.  It seems
> to happen whenever there's a "SimpleQuery: Unable to parse the query"
> error, however not when there's an "pool_send_and_wait: Error or
> notice message from backend" type of error.
> For example, this is the sort of error where knowing which client
> issued the query would be useful:
> ###########
> 2012-09-06 12:24:26 LOG:   pid 21763: pool_send_and_wait: Error or
> notice message from backend: : DB node id: 0 backend pid: 9508
> statement: INSERT into wsm
> (build_type,current_status,info,cudacode,gpu,subtest,os,arch,cl,dispvers,branch,ddcl,testdcmd,osversion)
> 				VALUES ('release','wsm','http://cuda-ljf0/wsm-release-2012-09-06-1346959467.log','2012-09-06.cuda-ljf0.release',
> 				'129','CUDA
> wsm','WINXP','x86_64','9306','315.47','cuda_a','21622','Cn4UlJYZBQfQ643CUnp8doAufFa7pKytzzBprGirF1EMSEqQ7cc1jk2aXDiSOpxt1Vpn61FrXpRY9oDzDvKiFwd5zN46TtRF3dkGT0f89','5RKMVBZIsECwQI2S7K');
> 				SELECT currval('wsm_id_seq'); message: relation "wsm" does not exist
> ###########
> Is this something that I can configure now, or will it require code
> based changes to pgpool?
> thanks!
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general

More information about the pgpool-general mailing list