Menu
▾
▴
Re: [Postgres-xc-developers] Configuration file for GTM
|
From: Koichi S. <ko...@in...> - 2011-07-25 02:54:37
|
Hi, I think introducing sections like [gtm] may make configuration files easier to review. I have a couple of issues on this though. 1) Users can append any configuration lines to postgresql.conf to disable any preceding options. This may be a bit difficult because users have to find the last like of the section. We can allow to appear same section any time to override but this will not help simple configuration file review. 2) I'm considering to reuse guc-files.l and guc.c which does not support the section now. I think user comment can serve as section header too. To minimize the code to write, and to make any *.conf file as compatible as possible, I'd like to inherit the current postgresql.conf file format unless there's other background of sections. Like to have any ideas. --- Koichi On Sun, 24 Jul 2011 18:11:34 -0400 Pavan Deolasee <pav...@en...> wrote: > I think its a good idea to have a common conf file for gtm/proxy. We > can possibly have a section inside the conf file to identify gtm-only > or proxy-only parameters. > > Something along these lines: > > hostname= > port= > > [gtm] > start_xid= > > [gtm_proxy] > conn_string > num_threads > > (The conf parameter names are not well thought of above) > > Thanks, > Pavan > > On Sat, Jul 23, 2011 at 10:35 AM, Michael Paquier > <mic...@gm...> wrote: > > GTM parameters: > > 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, boolean Start as a GTM standby server. > > standby_conn_string, in the same model as what is done in recovery.conf for > > standby nodes. > > log_min_messages, minimum level of logs that are written. > > > > Proxy options: > > hostname, string, GTM server hostname/IP to listen. > > port, string, GTM server port number to listen. > > nodenum, integer, node number for GTM server. > > log_filename, name of log file in GTM data directory > > 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 > > log_min_messages, minimum level of logs that are written. > > > > Common options are: > > hostname, port, node number, log file name, log minimum messages. > > > > Proxy uses exclusively: > > 1) Connection string to GTM > > 2) worker thread number > > > > GTM uses: > > 1) Standby mode boolean > > 2) start XID > > 3) Connection string for a standby to connect to GTM > > > > Both have a lot in common. We may even use the same option name for > > connection string in the case of Proxy connecting to GTM and GTM-Standby > > connecting to GTM master. > > More than half of the options are the same. Making also configuration file > > having the same name for GTM and proxy may be also easier to understand for > > the users. > > -- > > Michael Paquier > > http://michael.otacoo.com > > > > ------------------------------------------------------------------------------ > > Storage Efficiency Calculator > > This modeling tool is based on patent-pending intellectual property that > > has been used successfully in hundreds of IBM storage optimization engage- > > ments, worldwide. Store less, Store more with what you own, Move data to > > the right place. Try It Now! > > http://www.accelacomm.com/jaw/sfnl/114/51427378/ > > _______________________________________________ > > Postgres-xc-developers mailing list > > Pos...@li... > > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > > > > > > > > -- > Pavan Deolasee > EnterpriseDB http://www.enterprisedb.com > > ------------------------------------------------------------------------------ > Magic Quadrant for Content-Aware Data Loss Prevention > Research study explores the data loss prevention market. Includes in-depth > analysis on the changes within the DLP market, and the criteria used to > evaluate the strengths and weaknesses of these DLP solutions. > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > _______________________________________________ > Postgres-xc-developers mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers > |
