diff options
| author | Michael P | 2011-10-31 06:48:40 +0000 |
|---|---|---|
| committer | Michael P | 2011-10-31 06:49:52 +0000 |
| commit | 7019d1e55b23589137cfd96958dcc87bc761bf6e (patch) | |
| tree | 004d3ab951d0c301c3d199e26ccc30b1af0c1f90 | |
| parent | f1bc248f74fb9298f1a2a708a0489a859eed23f8 (diff) | |
Clean up documentation regarding GUC parameters used for node connections
Those parameters have been deleted since support of Node DDL.
| -rw-r--r-- | doc-xc/src/sgml/config.sgmlin | 122 | ||||
| -rw-r--r-- | doc-xc/src/sgml/installation.sgmlin | 123 | ||||
| -rw-r--r-- | doc-xc/src/sgml/runtime.sgmlin | 83 |
3 files changed, 10 insertions, 318 deletions
diff --git a/doc-xc/src/sgml/config.sgmlin b/doc-xc/src/sgml/config.sgmlin index 7a28e9fbf2..3b33b7a4f9 100644 --- a/doc-xc/src/sgml/config.sgmlin +++ b/doc-xc/src/sgml/config.sgmlin @@ -6858,95 +6858,16 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) </listitem> </varlistentry> - <varlistentry id="guc-pgxc-node-id" xreflabel="pgxc_node_id"> - <term><varname>pgxc_node_id</varname> (<type>integer</type>)</term> + <varlistentry id="guc-pgxc-node-name" xreflabel="pgxc_node_name"> + <term><varname>pgxc_node_name</varname> (<type>integer</type>)</term> <indexterm> - <primary><varname>pgxc_node_id</> configuration parameter</primary> + <primary><varname>pgxc_node_name</> configuration parameter</primary> </indexterm> <listitem> <para> - Specifies the node id. Coordinators and datanodes with same - <varname>pgxc_node_id</> are distinguished. - This id starts with 1. - </para> - </listitem> - </varlistentry> - - <varlistentry id="guc-num-data-nodes" xreflabel="num_data_nodes"> - <term><varname>num_data_nodes</varname> (<type>integer</type>)</term> - <indexterm> - <primary><varname>num_data_nodes</> configuration parameter</primary> - </indexterm> - <listitem> - <para> - Reports the total number of datanodes in the cluster. - </para> - </listitem> - </varlistentry> - - <varlistentry id="guc-data-node-hosts" xreflabel="data_node_hosts"> - <term><varname>data_node_hosts</varname> (<type>string</type>)</term> - <indexterm> - <primary><varname>data_node_hosts</> configuration parameter</primary> - </indexterm> - <listitem> - <para> - Reports address of all the datanodes network address. - Addresses can be specified by IP address or host name. - To report multiple datanodes, use comma to separate them. - <varname>pgxc_data_id</> of the first entry is assumed 1. - </para> - </listitem> - </varlistentry> - - <varlistentry id="guc-data-node-ports" xreflabel="data_node_ports"> - <term><varname>data_node_ports</varname> (<type>string</type>)</term> - <indexterm> - <primary><varname>data_node_ports</> configuration parameter</primary> - </indexterm> - <listitem> - <para> - Reports the node number of each datanode as specified by - <varname>data_node_hosts</> - Use comma to separate port number. - </para> - </listitem> - </varlistentry> - - <varlistentry id="guc-num-coordinators" xreflabel="num_coordinators"> - <term><varname>num_coordinators</varname> (<type>integer</type>)</term> - <indexterm> - <primary><varname>num_coordinators</> configuration parameter</primary> - </indexterm> - <listitem> - <para> - Reports the number of coordinators in the cluster. - </para> - </listitem> - </varlistentry> - - <varlistentry id="guc-coordinator-hosts" xreflabel="coordinator_hosts"> - <term><varname>coordinator_hosts</varname> (<type>string</type>)</term> - <indexterm> - <primary><varname>coordinator_hosts</> configuration parameter</primary> - </indexterm> - <listitem> - <para> - Reports the host name or IP address of all the coordinator in the cluster. - Use comma to separate entries. - </para> - </listitem> - </varlistentry> - - <varlistentry id="guc-coordinator-ports" xreflabel="coordinator_ports"> - <term><varname>coordinator_ports</varname> (<type>string</type>)</term> - <indexterm> - <primary><varname>coordinator_ports</> configuration parameter</primary> - </indexterm> - <indexterm><primary>character set</></> - <listitem> - <para> - Reports the port number of all the coordinators as listed in <varname>coordinator_ports</>. + Specifies the node name. A node uses this parameter to identify itself + with <link linkend="catalog-pgxc-node"><structname>pgxc_node</structname> + </link>.nodename </para> </listitem> </varlistentry> @@ -6987,37 +6908,6 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) </listitem> </varlistentry> - <varlistentry id="guc-primary-data-node" xreflabel="primary_data_node"> - <term><varname>primary_data_node</varname> (<type>integer</type>)</term> - <indexterm> - <primary><varname>primary_data_node</> configuration parameter</primary> - </indexterm> - <listitem> - <para> - Reports the <varname>pgxc_node_id</> of the primary datanode. - To update replicated table, coordinator will update this - datanode first to avoid update conflicts. All the - coordinators should specify the same value for this parameter. - </para> - </listitem> - </varlistentry> - - <varlistentry id="guc-preferred-data-nodes" xreflabel="preferred_data_nodes"> - <term><varname>preferred_data_nodes</varname> (<type>string</type>)</term> - <indexterm> - <primary><varname>preferred_data_nodes</> configuration parameter</primary> - </indexterm> - <listitem> - <para> - Reports the list of the preferred data node. Coordinator will - choose preferred data node to read replicated tables. - Choosing local datanode will save the network workload and - shorten the response time. - Different parameter can be chosen in different coordinator. - </para> - </listitem> - </varlistentry> - </variablelist> </sect1> diff --git a/doc-xc/src/sgml/installation.sgmlin b/doc-xc/src/sgml/installation.sgmlin index 9b9d64ec64..3494cf0cbc 100644 --- a/doc-xc/src/sgml/installation.sgmlin +++ b/doc-xc/src/sgml/installation.sgmlin @@ -2409,114 +2409,13 @@ postgres$ <userinput>/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data</> </varlistentry> <varlistentry> - <term><envar>num_data_nodes</envar></term> + <term><envar>pgxc_node_name</envar></term> <listitem> &xconly; <para> - This parameter specifies how many datanodes the coordinator - connects to. - You should specify the same value to all the - coordinators. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><envar>data_node_hosts</envar></term> - <listitem> -&xconly; - <para> - Specify the list of IP address or host name of each data node - as character string. - You should specify the same value to all the - coordinators. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><envar>data_node_ports</envar></term> - <listitem> -&xconly; - <para> - Specify the list of port number of each data node - as character string in the order of <option>data_node_hosts</>. - You should specify the same value to all the - coordinators. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><envar>data_node_users</envar></term> - <listitem> -&xconly; - <para> - Specify the name of user (role) you use to connect to - datanodes. This option may be removed in future releases. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><envar>num_coordinators</envar></term> - <listitem> - <para> -&xconly; - Specify the list of IP address or host name of each coordinator - as character string. - You should specify the same value to all the - coordinators. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><envar>coordinator_hosts</envar></term> - <listitem> -&xconly; - <para> - Specify the list of IP address or host name of each coordinator - as character string. - You should specify the same value to all the - coordinators. - </para> - </listitem> - </varlistentry> - - - <varlistentry> - <term><envar>coordinator_ports</envar></term> - <listitem> -&xconly; - <para> - Specify the list of port number of each coordinator - as character string in the order of <option>coordinator_hosts</>. - You should specify the same value to all the - coordinators. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><envar>coordinator_users</envar></term> - <listitem> -&xconly; - <para> - Specify the name of user (role) you use to connect to - coordinators. This option may be removed in future releases. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><envar>pgxc_node_id</envar></term> - <listitem> -&xconly; - <para> - Specify the index of this coordinator. The index refers to the - element of <option>coordinator_hosts</> parameter, which begins - with 1. + Specify the name of this cluster node. This name index refers to the + element of <link linkend="catalog-pgxc-node"><structname>pgxc_node + </structname></link>.node_name value, to identify the node self. </para> </listitem> </varlistentry> @@ -2607,20 +2506,6 @@ postgres$ <userinput>/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data</> </listitem> </varlistentry> - <varlistentry> - <varlistentry> - <term><envar>pgxc_node_id</envar></term> - <listitem> -&xconly; - <para> - Specify the index of the datanode. The index refers to the - element of <option>data_node_hosts</> parameter specified in - the coordinator <filename>postgresql.conf</>, which begins - with 1. - </para> - </listitem> - </varlistentry> - <term><envar>gtm_port</envar></term> <listitem> &xconly; diff --git a/doc-xc/src/sgml/runtime.sgmlin b/doc-xc/src/sgml/runtime.sgmlin index c8059cf84e..4ba1b4947b 100644 --- a/doc-xc/src/sgml/runtime.sgmlin +++ b/doc-xc/src/sgml/runtime.sgmlin @@ -649,89 +649,6 @@ $ <userinput>gtm_ctl start -S gtm_proxy -i 1 -D /usr/local/pgsql/gtm_proxy -i 1 </listitem> </varlistentry> - <varlistentry> - <term>num_data_nodes</term> - <listitem> - <para> - Specifies the number of datanodes in the cluster. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>data_node_hosts</term> - <listitem> - <para> - Specifies the list of host name or IP addresses of all the - datanodes. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>data_node_ports</term> - <listitem> - <para> - Specifies the list of the port number of all the - datanodes. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>preferred_data_nodes</term> - <listitem> - <para> - Specifies the list of datanode IDs used as preferred data node. - When coordinator reads replicated tables, it is efficient to read - them from the datanode running locally. - You can specify different value for each coordinator. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Primary_data_node</term> - <listitem> - <para> - Specifies the datanode IDs used as primary datanode. - When coordinator writes to replicated tables, first attempt is - done to the primary data node to avoid inconsistent updates among - datanodes. - You should specify same value for all the coordinator. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>num_coordinators</term> - <listitem> - <para> - Specifies the number of coordinators in the cluster. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>coordinator_hosts</term> - <listitem> - <para> - Specifies the list of host name or IP addresses of all the - coordinators. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>coordinator_ports</term> - <listitem> - <para> - Specifies the list of the port number of all the - coordinators. - </para> - </listitem> - </varlistentry> - </variablelist> </sect2> |
