postgres-xc-developers Mailing List for Postgres-XC

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

I don't care about the name, but I'd like to see what configuration
parameters GTM and GTM-Proxy should need.  If they're very different,
there will be no reason to have the same configuration file name.

I believe introduction of GUC code should independent from HA support
and should be treated as separate patches.   This is why I'd like to
have this before further effort of HA related improvements.

Regards;
----------
Koichi Suzuki



2011/7/23 Michael Paquier <mic...@gm...>:
>
>
> On Thu, Jul 21, 2011 at 3:52 PM, Koichi Suzuki <ko...@in...>
> wrote:
>>
>> I totally agree with having gtm.conf and gtm_proxy.conf to reduce the
>> number of runt-time options, especially those passed with -o option from
>> gtm_ctl.
>
> About the configuration file, perhaps GTM and GTM-proxy could use a
> configuration file with the same name.
> I would imagine that if the guc APIs of postgresql are brought in GTM it
> will be included in gtm/common so as a base it looks more consistent to use
> the same file name: gtm.conf.
>>
>> I need to bring code for GUC from postgres.   Could be done as a part of
>> additional HA feature development.
>
> If you want to include that in the HA effort, it could be nice to make
> separate patches for the configuration file and GTM-Standby additional
> features.
> It will make commit comprehension simpler.
> --
> 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
>
>

On Thu, Jul 21, 2011 at 3:52 PM, Koichi Suzuki <ko...@in...>wrote:

> I totally agree with having gtm.conf and gtm_proxy.conf to reduce the
> number of runt-time options, especially those passed with -o option from
> gtm_ctl.
>
About the configuration file, perhaps GTM and GTM-proxy could use a
configuration file with the same name.
I would imagine that if the guc APIs of postgresql are brought in GTM it
will be included in gtm/common so as a base it looks more consistent to use
the same file name: gtm.conf.

>
> I need to bring code for GUC from postgres.   Could be done as a part of
> additional HA feature development.
>
If you want to include that in the HA effort, it could be nice to make
separate patches for the configuration file and GTM-Standby additional
features.
It will make commit comprehension simpler.
-- 
Michael Paquier
http://michael.otacoo.com

Thanks.
I will try to have a look at your patch as soon as possible.
Regards,
-- 
Michael Paquier
http://michael.otacoo.com