From: Michael P. <mic...@gm...> - 2011-07-21 06:43:18
|
Hi, In the same model as postgresql.conf, why not creating a configuration file only for GTM/Proxy? This advantage of that could be the reduction of call parameters for GTM and proxy Here is the list of parameters that could be used: hostname, string, GTM server hostname/IP to listen. port, string, GTM server port number to listen. nodenum, integer, node number for GTM server. start_xid, integer, start value of GXID feed log_filename, name of log file in GTM data directory Standby options standby, boolean Start as a GTM standby server. standby_conn_string, in the same model as what is done in recovery.conf for standby nodes. Proxy options: gtm_conn_string, connection string to use when contacting GTM (This string is completed with nodeID when registering) worker_thread_num, integer, number of worker threads Other options: log_min_messages, minimum level of logs that are written. The main purpose of this initiative is to have: 1) an easier configuration interface for GTM and proxy 2) have a control on the logs GTM write, now GTM writes a large quantity of logs and log file can reach easily several GB after 1 hour of run. For the implementation, it could be possible to use the guc interface but I am not that much familiar with that. Any thoughts? Complementary ideas? -- Michael Paquier http://michael.otacoo.com |