gtm gtm 1 Application gtm provides global transaction management for the Postgres-XL across the entire cluster. gtm option Description The GTM provides consistent transaction management fully compatible with vanilla PostgreSQL. It is highly advised to start and stop the GTM using gtm_ctl(8). You must provide a GTM configuration file gtm.conf placed in the GTM working directory as specified by -D command line option. The configuration file specifies the GTM running environment and resources. Some of the parameters specified in the control file can be overridden by command line options. As with other cluster components, the recommended method of configuring and managing them is with the utility. Configuration File GTM configuration parameters are specified in the configuration file gtm.confgtm.conf placed in the working directory specified as -D option of gtm command line option as described in the next section. The format of the configuration file is patterned after the postgresql.conf. The options are as follows. active_host (string) active_host configuration parameter Specifies the listen addresses (host name or IP address) of active gtm. This parameter is effective only when this gtm is specified as a standby. There is no default value for this parameter. active_port (integer) active_port configuration parameter Specifies the port number of active gtm. This parameter is effective only when this gtm is specified as a GTM standby. The standby connects to the primary gtm to obtain a stream of updates of transaction status values. There is no default value for this parameter. keepalives_count (integer) keepalives_count (integer) Specifies keepalives_count option for the connection to gtm. This option is effective only when it runs as a GTM Standby. The default value is zero and keepalives feature is disabled. keepalives_idle (integer) keepalives_idle (integer) Specifies keepalives_idle option for the connection to gtm. This option is effective only when it runs as a GTM Standby. The default value is zero and keepalives feature is disabled. keepalives_interval (integer) keepalives_interval (integer) Specifies keepalives_interval option for the connection to gtm. This option is effective only when it runs as a GTM Standby. The default value is zero and keepalives feature is disabled. listen_addresses (string) listen_addresses configuration parameter Specifies listen addresses (host name or IP address) of this gtm or gtm standby. Default value is '*'. log_file (string) log_file configuration parameter Specifies log file name. This file will be created in the working directory of this gtm as specified by -D command line option. The default is gtm.log. log_min_messages (enum) log_min_messages configuration parameter Controls which message levels are written to the log. Valid values are DEBUG, DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, INFO, NOTICE, WARNING, ERROR, LOG, FATAL and PANIC. Each level includes all the levels that follow it. The later the level, the fewer messages are sent. The default is WARNING. nodename (string) nodename configuration parameter Specifies the name of this gtm or gtm standby. There is no default value for this parameter. port (integer) port configuration parameter Specifies the port number of gtm or gtm standby. Default value is 6666. startup (enum) startup configuration parameter Specifies the startup mode of this gtm. Valied values are act or standby. act means to start up this gtm as usual so that gtm clients (Coordinators, data nodes or gtm-proxies) can connect for transaction management. standby means this gtm starts up as a backup of act gtm. standby gtm can be promoted to act when act fails. synchronous-backup (boolean) synchronous-backup configuration parameter Specifies if the backup to the GTM-Standby is taken synchronously. If this is turned on, the GTM will send and receive synchronize message to make sure that all the backups reached to the standby. If it is turned off, all the backup information will be sent without checking they reached the GTM-Standby. Default value is off. Options Options are specified with preceding '-', each option may be associated with a value. They can be specified in -o option of gtm_ctl(8). Parameters specified as command line options override these specified in the configuration file described in the previous section. Options are as follows: Specify a directory which holds data for gtm or gtm_proxy Specify a log file for gtm_ctl. Specify the global transaction ID to start with. This is needed when you start gtm for the first time because initdb consumes XID locally and gtm should start to give GXID greater than the last one each initdb consumed locally. If gtm has been shut down gracefully, then this value will be taken from the last run. If -x option is not specified at the first run, initial global transaction ID value will be set to a default initial value which is considered to be safe enough (in version &version;, it is 10000). If many statements are involved in initdb, you should consider to increasing this value. To find the precise value to start with, you should run pg_controldata to find Latest checkpoint's NextXID of all the Coordinators and Datanodes and choose the value larger than or equals to the maximum value found. Specify host name or IP address used. Specify port number to listen. When starting a GTM as a standby instance, the following options can also be provided. Specify if the GTM starts as a standby Specify host name or IP address of the active GTM instance to connect to Specify port number of the active GTM instance to connect to