Fix documentations for 6 parameters.
Japanese docs too.
"log_standby_delay"
"log_backend_messages"
"wd_lifecheck_method"
"memqcache_method"
"disable_load_balance_on_write"
"backend_clustering_mode"
</varlistentry>
<varlistentry id="guc-log-backend-messages" xreflabel="log_backend_messages">
- <term><varname>log_backend_messages</varname> (<type>boolean</type>)
+ <term><varname>log_backend_messages</varname> (<type>enum</type>)
<indexterm>
<!--
<primary><varname>log_backend_messages</varname> configuration parameter</primary>
<para>
このモードはもっともよく使われており、推薦できるクラスタリングモードです。
このモードでは<productname>PostgreSQL</productname>が個々のサーバをレプリケーションします。
- このモードを有効にするには<varname>backend_clustering_mode</varname>に'streaming_replication'を設定してください。
+ このモードを有効にするには<varname>backend_clustering_mode</varname>にstreaming_replicationを設定してください。
<programlisting>
-backend_clustering_mode = 'streaming_replication'
+backend_clustering_mode = streaming_replication
</programlisting>
このモードでは127台までのストリーミングレプリケーションスタンバイサーバを使用できます。
また、スタンバイサーバをまったく使用しないことも可能です。
between <productname>PostgreSQL</> backends.
-->
このモードでは<productname>PostgreSQL</>間のデータレプリケーションを<productname>Pgpool-II</productname>に行わせます。
- このモードを有効にするには<varname>backend_clustering_mode</varname>に'native_replication'を設定してください。
+ このモードを有効にするには<varname>backend_clustering_mode</varname>にnative_replicationを設定してください。
<programlisting>
-backend_clustering_mode = 'native_replication'
+backend_clustering_mode = native_replication
</programlisting>
このモードでは127台までのレプリカサーバを使用できます。
また、レプリカサーバをまったく使用しないことも可能です。
<para>
このモードは、ネイティブレプリケーションモードと似ていますが、更にノードをまたがる可視性の一貫性を保証します。
実装は研究論文<xref linkend="mishima2009">に基づいています。
- このモードを有効にするには<varname>backend_clustering_mode</varname>に'snapshot_isolation'を設定してください。
+ このモードを有効にするには<varname>backend_clustering_mode</varname>にsnapshot_isolationを設定してください。
<programlisting>
-backend_clustering_mode = 'snapshot_isolation'
+backend_clustering_mode = snapshot_isolation
</programlisting>
たとえば、以下のようなノードにまたがる可視性の一貫性がないことからくるノード間のデータ不整合を防ぐことができます。
ここで、S1, S2はセッションを表し、N1, N2はPostgreSQLのサーバ1と2を表します。
<para>
このモードでは<productname>PostgreSQL</productname>が個々のサーバをレプリケーションします。
- このモードを有効にするには<varname>backend_clustering_mode</varname>に'logical_replication'を設定してください。
+ このモードを有効にするには<varname>backend_clustering_mode</varname>にlogical_replicationを設定してください。
<programlisting>
-backend_clustering_mode = 'logical_replication'
+backend_clustering_mode = logical_replication
</programlisting>
このモードでは127台までのロジカルレプリケーションサーバを使用できます。
また、スタンバイサーバをまったく使用しないことも可能です。
<para>
このモードでは<productname>Pgpool-II</productname>を<acronym>Slony-I</acronym>と組み合わせて使用します。
Slony-Iが実際にデータのレプリケーションを行います。
- このモードを有効にするには<varname>backend_clustering_mode</varname>に'slony'を設定してください。
+ このモードを有効にするには<varname>backend_clustering_mode</varname>にslonyを設定してください。
<programlisting>
-backend_clustering_mode = 'slony'
+backend_clustering_mode = slony
</programlisting>
このモードでは127台までのレプリカサーバを使用できます。
また、レプリカサーバをまったく使用しないことも可能です。
このモードでは、<productname>Pgpool-II</>はデータベースの同期に関しては関与しません。
システム全体に意味の有る動作をさせるのはユーザの責任となります。
このモードでは負荷分散は<emphasis>できません</emphasis>。
- このモードを有効にするには<varname>backend_clustering_mode</varname>に'raw'を設定してください。
+ このモードを有効にするには<varname>backend_clustering_mode</varname>にrawを設定してください。
<programlisting>
-backend_clustering_mode = 'raw'
+backend_clustering_mode = raw
</programlisting>
</para>
</sect2>
from <filename>pgpool.conf.sample</filename>.
Make sure your <filename>pgpool.conf</filename> includes following line:
<programlisting>
-backend_clustering_mode = 'streaming_replication'
+backend_clustering_mode = streaming_replication
</programlisting>
-->
<filename>pgpool.conf.sample</filename>をコピーして<filename>pgpool.conf</filename>を作ります。
以下の行が<filename>pgpool.conf</filename>に含まれていることを確認してください。
<programlisting>
-backend_clustering_mode = 'streaming_replication'
+backend_clustering_mode = streaming_replication
</programlisting>
</para>
</listitem>
</para>
<programlisting>
[root@server1 ~]# vi /etc/pgpool-II/pgpool.conf
-backend_clustering_mode = 'streaming_replication'
+backend_clustering_mode = streaming_replication
</programlisting>
</sect3>
ネイティブレプリケーションモードの場合
</para>
<programlisting>
-backend_clustering_mode = 'native_replication'
+backend_clustering_mode = native_replication
</programlisting>
</listitem>
<listitem>
スナップショットアイソレーションモードの場合
</para>
<programlisting>
-backend_clustering_mode = 'snapshot_isolation'
+backend_clustering_mode = snapshot_isolation
</programlisting>
</listitem>
</itemizedlist>
</varlistentry>
<varlistentry id="guc-disable-load-balance-on-write" xreflabel="disable_load_balance_on_write">
- <term><varname>disable_load_balance_on_write</varname> (<type>string</type>)
+ <term><varname>disable_load_balance_on_write</varname> (<type>enum</type>)
<indexterm>
<!--
<primary><varname>disable_load_balance_on_write</varname> configuration parameter</primary>
<variablelist>
<varlistentry id="guc-memqcache-method" xreflabel="memqcache_method">
- <term><varname>memqcache_method</varname> (<type>string</type>)
+ <term><varname>memqcache_method</varname> (<type>enum</type>)
<indexterm>
<!--
<primary><varname>memqcache_method</varname> configuration parameter</primary>
<tbody>
<row>
- <entry><literal>'shmem'</literal></entry>
+ <entry><literal>shmem</literal></entry>
<!--
<entry>Use shared memory</entry>
-->
</row>
<row>
- <entry><literal>'memcached'</literal></entry>
+ <entry><literal>memcached</literal></entry>
<!--
<entry>Use <ulink url="http://memcached.org/">memcached</ulink></entry>
-->
<para>
<!--
- Default is <literal>'shmem'</literal>.
+ Default is <literal>shmem</literal>.
-->
- デフォルトは<literal>'shmem'</literal>です。
+ デフォルトは<literal>shmem</literal>です。
</para>
<para>
</varlistentry>
<varlistentry id="guc-log-standby-delay" xreflabel="log_standby_delay">
- <term><varname>log_standby_delay</varname> (<type>string</type>)
+ <term><varname>log_standby_delay</varname> (<type>enum</type>)
<indexterm>
<!--
<primary><varname>log_standby_delay</varname> configuration parameter</primary>
<tbody>
<row>
- <entry><literal>'none'</literal></entry>
+ <entry><literal>none</literal></entry>
<!--
<entry>Never log the standby delay</entry>
-->
</row>
<row>
- <entry><literal>'always'</literal></entry>
+ <entry><literal>always</literal></entry>
<!--
<entry>Log the standby delay, every time the replication delay is checked</entry>
-->
</row>
<row>
- <entry><literal>'if_over_threshold'</literal></entry>
+ <entry><literal>if_over_threshold</literal></entry>
<!--
<entry>Only log the standby delay, when it exceeds <xref linkend="guc-delay-threshold"> value</entry>
-->
<variablelist>
<varlistentry id="guc-wd-lifecheck-method" xreflabel="wd_lifecheck_method">
- <term><varname>wd_lifecheck_method</varname> (<type>string</type>)
+ <term><varname>wd_lifecheck_method</varname> (<type>enum</type>)
<indexterm>
<!--
<primary><varname>wd_lifecheck_method</varname> configuration parameter</primary>
<listitem>
<para>
<!--
- Specifies the method of life check. This can be either of <literal>'heartbeat'</literal> (default),
- <literal>'query'</literal> or <literal>'external'</literal>.
+ Specifies the method of life check. This can be either of <literal>heartbeat</literal> (default),
+ <literal>query</literal> or <literal>external</literal>.
-->
死活監視の方法を指定します。
- 指定できる値は <literal>'heartbeat'</literal> (デフォルト)、<literal>'query'</literal>、または<literal>'external'</literal> です。
+ 指定できる値は <literal>heartbeat</literal> (デフォルト)、<literal>query</literal>、または<literal>external</literal> です。
</para>
<para>
<!--
If there are no signal for a certain period, watchdog regards is as failure
of the <productname>Pgpool-II</productname> .
-->
- <literal>'heartbeat'</literal>を指定した場合には、監視は「ハートビートモード」で行われます。
+ <literal>heartbeat</literal>を指定した場合には、監視は「ハートビートモード」で行われます。
watchdog は一定間隔でハートビート信号(UDP パケット)を他の<productname>Pgpool-II</productname>へ送信します。
またwatchdogは他の<productname>Pgpool-II</productname>から送られてくる信号を受信します。
これが一定時間以上途絶えた場合にはその<productname>Pgpool-II</productname>に障害が発生したと判断します。
</varlistentry>
<varlistentry id="guc-log-backend-messages" xreflabel="log_backend_messages">
- <term><varname>log_backend_messages</varname> (<type>boolean</type>)
+ <term><varname>log_backend_messages</varname> (<type>enum</type>)
<indexterm>
<primary><varname>log_backend_messages</varname> configuration parameter</primary>
</indexterm>
This mode is most popular and recommended clustering mode. In this
mode <productname>PostgreSQL</productname> is responsible to
replicate each servers. To enable this mode, use
- 'streaming_replication' for
+ streaming_replication for
<varname>backend_clustering_mode</varname>.
<programlisting>
-backend_clustering_mode = 'streaming_replication'
+backend_clustering_mode = streaming_replication
</programlisting>
In this mode you can have up to 127 streaming replication standby servers.
Also it is possible not to have standby server at all.
<para>
This mode makes the <productname>Pgpool-II</productname> to
replicate data between <productname>PostgreSQL</productname>
- backends. To enable this mode, use 'native_replication' for
+ backends. To enable this mode, use native_replication for
<varname>backend_clustering_mode</varname>.
<programlisting>
-backend_clustering_mode = 'native_replication'
+backend_clustering_mode = native_replication
</programlisting>
In this mode you can have up to 127 standby replication servers.
Also it is possible not to have standby server at all.
This mode is similar to the native replication mode except it adds
the visibility consistency among nodes. The implementation is based
on a research paper <xref linkend="mishima2009">.
- To enable this mode, use 'snapshot_isolation' for
+ To enable this mode, use snapshot_isolation for
<varname>backend_clustering_mode</varname>.
<programlisting>
-backend_clustering_mode = 'snapshot_isolation'
+backend_clustering_mode = snapshot_isolation
</programlisting>
For example, you can avoid following inconsistency among nodes caused by the
visibility inconsistency. Here S1 and S2 denotes sessions, while N1
<para>
In this mode
<productname>PostgreSQL</productname> is responsible to replicate
- each servers. To enable this mode, use 'logical_replication' for
+ each servers. To enable this mode, use logical_replication for
<varname>backend_clustering_mode</varname>.
<programlisting>
-backend_clustering_mode = 'logical_replication'
+backend_clustering_mode = logical_replication
</programlisting>
In this mode you can have up to 127 logical replication standby servers.
Also it is possible not to have standby server at all.
<para>
This mode is used to couple <productname>Pgpool-II</productname>
with <acronym>Slony-I</acronym>. Slony-I is responsible for doing
- the actual data replication. To enable this mode, use 'slony' for
+ the actual data replication. To enable this mode, use slony for
<varname>backend_clustering_mode</varname>.
<programlisting>
-backend_clustering_mode = 'slony'
+backend_clustering_mode = slony
</programlisting>
In this mode you can have up to 127 replica servers. Also it is
possible not to have replica server at all.
In this mode, <productname>Pgpool-II</> does not care about the database synchronization.
It's user's responsibility to make the whole system does a meaningful thing.
Load balancing is <emphasis>not</emphasis> possible in the mode.
- To enable this mode, use 'raw' for <varname>backend_clustering_mode</varname>.
+ To enable this mode, use raw for <varname>backend_clustering_mode</varname>.
<programlisting>
-backend_clustering_mode = 'raw'
+backend_clustering_mode = raw
</programlisting>
</para>
</sect2>
from <filename>pgpool.conf.sample</filename>.
Make sure your <filename>pgpool.conf</filename> includes following line:
<programlisting>
-backend_clustering_mode = 'streaming_replication'
+backend_clustering_mode = streaming_replication
</programlisting>
</para>
</listitem>
</para>
<programlisting>
[root@server1 ~]# vi /etc/pgpool-II/pgpool.conf
-backend_clustering_mode = 'streaming_replication'
+backend_clustering_mode = streaming_replication
</programlisting>
</sect3>
Native replication mode
</para>
<programlisting>
-backend_clustering_mode = 'native_replication'
+backend_clustering_mode = native_replication
</programlisting>
</listitem>
<listitem>
Snapshot isolation mode
</para>
<programlisting>
-backend_clustering_mode = 'snapshot_isolation'
+backend_clustering_mode = snapshot_isolation
</programlisting>
</listitem>
</itemizedlist>
</varlistentry>
<varlistentry id="guc-disable-load-balance-on-write" xreflabel="disable_load_balance_on_write">
- <term><varname>disable_load_balance_on_write</varname> (<type>string</type>)
+ <term><varname>disable_load_balance_on_write</varname> (<type>enum</type>)
<indexterm>
<primary><varname>disable_load_balance_on_write</varname> configuration parameter</primary>
</indexterm>
<variablelist>
<varlistentry id="guc-memqcache-method" xreflabel="memqcache_method">
- <term><varname>memqcache_method</varname> (<type>string</type>)
+ <term><varname>memqcache_method</varname> (<type>enum</type>)
<indexterm>
<primary><varname>memqcache_method</varname> configuration parameter</primary>
</indexterm>
<tbody>
<row>
- <entry><literal>'shmem'</literal></entry>
+ <entry><literal>shmem</literal></entry>
<entry>Use shared memory</entry>
</row>
<row>
- <entry><literal>'memcached'</literal></entry>
+ <entry><literal>memcached</literal></entry>
<entry>Use <ulink url="http://memcached.org/">memcached</ulink></entry>
</row>
If you are not sure which memqcache_method to be used, start with <varname>shmem</varname>.
</para>
<para>
- Default is <literal>'shmem'</literal>.
+ Default is <literal>shmem</literal>.
</para>
<para>
</varlistentry>
<varlistentry id="guc-log-standby-delay" xreflabel="log_standby_delay">
- <term><varname>log_standby_delay</varname> (<type>string</type>)
+ <term><varname>log_standby_delay</varname> (<type>enum</type>)
<indexterm>
<primary><varname>log_standby_delay</varname> configuration parameter</primary>
</indexterm>
<tbody>
<row>
- <entry><literal>'none'</literal></entry>
+ <entry><literal>none</literal></entry>
<entry>Never log the standby delay</entry>
</row>
<row>
- <entry><literal>'always'</literal></entry>
+ <entry><literal>always</literal></entry>
<entry>Log the standby delay if it's greater than 0, every time the replication delay is checked</entry>
</row>
<row>
- <entry><literal>'if_over_threshold'</literal></entry>
+ <entry><literal>if_over_threshold</literal></entry>
<entry>Only log the standby delay, when it exceeds <xref linkend="guc-delay-threshold"> or <xref linkend="guc-delay-threshold-by-time"> value (the default)</entry>
</row>
</tbody>
<variablelist>
<varlistentry id="guc-wd-lifecheck-method" xreflabel="wd_lifecheck_method">
- <term><varname>wd_lifecheck_method</varname> (<type>string</type>)
+ <term><varname>wd_lifecheck_method</varname> (<type>enum</type>)
<indexterm>
<primary><varname>wd_lifecheck_method</varname> configuration parameter</primary>
</indexterm>
</term>
<listitem>
<para>
- Specifies the method of life check. This can be either of <literal>'heartbeat'</literal> (default),
- <literal>'query'</literal> or <literal>'external'</literal>.
+ Specifies the method of life check. This can be either of <literal>heartbeat</literal> (default),
+ <literal>query</literal> or <literal>external</literal>.
</para>
<para>
<literal>heartbeat</literal>: In this mode, watchdog sends the heartbeat signals (<acronym>UDP</acronym> packets)
#------------------------------------------------------------------------------
# BACKEND CLUSTERING MODE
-# Choose one of: 'streaming_replication', 'native_replication',
-# 'logical_replication', 'slony', 'raw' or 'snapshot_isolation'
+# Choose one of: streaming_replication, native_replication,
+# logical_replication, slony, raw or snapshot_isolation
# (change requires restart)
#------------------------------------------------------------------------------
-backend_clustering_mode = 'streaming_replication'
+backend_clustering_mode = streaming_replication
#------------------------------------------------------------------------------
# CONNECTIONS
# Log any backend messages
# Valid values are none, terse and verbose
-#log_standby_delay = 'if_over_threshold'
+#log_standby_delay = if_over_threshold
# Log standby delay
# Valid values are combinations of always,
# if_over_threshold, none
# If off, SQL comments effectively prevent the judgment
# (pre 3.4 behavior).
-#disable_load_balance_on_write = 'transaction'
+#disable_load_balance_on_write = transaction
# Load balance behavior when write query is issued
# in an explicit transaction.
#
# Valid values:
#
- # 'transaction' (default):
+ # transaction (default):
# if a write query is issued, subsequent
# read queries will not be load balanced
# until the transaction ends.
#
- # 'trans_transaction':
+ # trans_transaction:
# if a write query is issued, subsequent
# read queries in an explicit transaction
# will not be load balanced until the session ends.
#
- # 'dml_adaptive':
+ # dml_adaptive:
# Queries on the tables that have already been
# modified within the current explicit transaction will
# not be load balanced until the end of the transaction.
#
- # 'always':
+ # always:
# if a write query is issued, read queries will
# not be load balanced until the session ends.
#
# Note that any query not in an explicit transaction
- # is not affected by the parameter except 'always'.
+ # is not affected by the parameter except always.
#dml_adaptive_object_relationship_list= ''
# comma separated list of object pairs
# example: 'tb_t1:tb_t2,insert_tb_f_func():tb_f,tb_v:my_view'
# Note: function name in this list must also be present in
# the write_function_list
- # only valid for disable_load_balance_on_write = 'dml_adaptive'.
+ # only valid for disable_load_balance_on_write = dml_adaptive.
#statement_level_load_balance = off
# Enables statement level load balancing
# '' to disable monitoring
# (change requires restart)
-#wd_lifecheck_method = 'heartbeat'
- # Method of watchdog lifecheck ('heartbeat' or 'query' or 'external')
+#wd_lifecheck_method = heartbeat
+ # Method of watchdog lifecheck (heartbeat or query or external)
# (change requires restart)
#wd_interval = 10
# lifecheck interval (sec) > 0
#memory_cache_enabled = off
# If on, use the memory cache functionality, off by default
# (change requires restart)
-#memqcache_method = 'shmem'
- # Cache storage method. either 'shmem'(shared memory) or
- # 'memcached'. 'shmem' by default
+#memqcache_method = shmem
+ # Cache storage method. either shmem(shared memory) or
+ # memcached. shmem by default
# (change requires restart)
#memqcache_memcached_host = 'localhost'
# Memcached host name or IP address. Mandatory if
- # memqcache_method = 'memcached'.
+ # memqcache_method = memcached.
# Defaults to localhost.
# (change requires restart)
#memqcache_memcached_port = 11211
- # Memcached port number. Mandatory if memqcache_method = 'memcached'.
+ # Memcached port number. Mandatory if memqcache_method = memcached.
# Defaults to 11211.
# (change requires restart)
#memqcache_total_size = 64MB
# Total memory size in bytes for storing memory cache.
- # Mandatory if memqcache_method = 'shmem'.
+ # Mandatory if memqcache_method = shmem.
# Defaults to 64MB.
# (change requires restart)
#memqcache_max_num_cache = 1000000
# Total number of cache entries. Mandatory
- # if memqcache_method = 'shmem'.
+ # if memqcache_method = shmem.
# Each cache entry consumes 48 bytes on shared memory.
# Defaults to 1,000,000(45.8MB).
# (change requires restart)
# Must be smaller than memqcache_cache_block_size. Defaults to 400KB.
# (change requires restart)
#memqcache_cache_block_size = 1MB
- # Cache block size in bytes. Mandatory if memqcache_method = 'shmem'.
+ # Cache block size in bytes. Mandatory if memqcache_method = shmem.
# Defaults to 1MB.
# (change requires restart)
#memqcache_oiddir = '/var/log/pgpool/oiddir'