Now GTM has no option to control verbosity of the log. Because current gtm log is like "verbose" in PostgreSQL, every line of log is associated with LCOATION ...., which is too much for usual operation.
All the log lines look like
---------------
LOCATION: ProcessPGXCNodeRegister, register_gtm.c:116
3:1138735424:2012-11-06 22:44:55.013 JST -LOG: Recovery_PGXCNodeRegister Request info: type=1, nodename=gtm_pxy3, port=20001,datafolder=/home/koichi/pgxc/nodes/gtm_pxy, ipaddress=*, status=0
LOCATION: Recovery_PGXCNodeRegister, register_common.c:397
4:1138735424:2012-11-06 22:44:55.013 JST -LOG: Recovery_PGXCNodeRegister Node info: type=1, nodename=gtm_pxy3, port=20001, datafolder=/home/koichi/pgxc/nodes/gtm_pxy, ipaddress=*, status=0
---------------
GTM should provide log_error_verbosity option to control it.