Patch is created by Umar Hayat.
以下のテーブルはメッセージフィールドの詳細な説明です。
</para>
- <table id="wd-ipc-resutl-format-table">
+ <table id="wd-ipc-result-format-table">
<!--
<title>Watchdog IPC result packet format</title>
-->
Since <productname>Pgpool-II</productname> is a middleware that works between
<productname>PostgreSQL</> servers and a <productname>PostgreSQL</> database client, so when a client application
connects to the <productname>Pgpool-II</productname>, <productname>Pgpool-II</productname>
- inturn connects to the <productname>PostgreSQL</> servers using the same credentials to serve the incomming
+ inturn connects to the <productname>PostgreSQL</> servers using the same credentials to serve the incoming
client connection. Thus, all the access privileges and restrictions defined for the user in <productname>PostgreSQL</>
gets automatically applied to all <productname>Pgpool-II</productname> clients, with an exceptions of
the authentications on <productname>PostgreSQL</> side that depends on the client's IP addresses or hostnames.
<productname>Pgpool-II</productname> server and not that of the actual client.
Therefore, for the client host based authentications <productname>Pgpool-II</productname> has the
<literal>pool_hba</literal> mechanism similar to the <literal>pg_hba</literal> mechanism for
- authenticating the incomming client connections.
+ authenticating the incoming client connections.
-->
<productname>Pgpool-II</productname>は<productname>PostgreSQL</>サーバと<productname>PostgreSQL</>データベースクライアントの間で動作するミドルウェアであるため、クライアントアプリケーションが<productname>Pgpool-II</productname>に接続したときには、今度は<productname>Pgpool-II</productname>がクライアントが提供したのと同じ認証情報を使って<productname>PostgreSQL</>サーバに接続します。
したがって、<productname>PostgreSQL</>のユーザに対し定義された全てのアクセス権限と制約が、自動的に全ての<productname>Pgpool-II</productname>クライアントに適用されます。
<!--
You can avoid maintaining <filename>pool_passwd</filename> by
using <xref linkend="guc-allow-clear-text-frontend-auth"> as well
- but it does not enfornce to use SSL encryption because
+ but it does not enforce to use SSL encryption because
<filename>pool_hba.conf</filename> cannot be used with the
parameter.
-->
<para>
<!--
- This authentication method uses LDAP as the password cerification method.
+ This authentication method uses LDAP as the password certification method.
LDAP is used only to validate the user name/password pairs. Therefore the user must
already exist in the database before LDAP can be used for authentication.
-->
<listitem>
<para>
<!--
- Set to 1 to make the password used for LDAP authentication use authetication
+ Set to 1 to make the password used for LDAP authentication use authentication
between <productname>Pgpool-II</productname> and backend.
-->
1に設定すると、LDAP認証で使用されたパスワードを<productname>Pgpool-II</productname>とバックエンド間の認証に使用します。
It is an error to mix configuration options for simple bind with options
for search+bind.
-->
-seartch/bindオプションと単純バインドに対するオプションの設定を混在させるのはエラーです。
+search/bindオプションと単純バインドに対するオプションの設定を混在させるのはエラーです。
</para>
<para>
<para>
<!--
- But serialization has its own overheads, and it is recomended
+ But serialization has its own overheads, and it is recommended
to be used only with the larger values of <xref linkend="guc-num-init-children">.
For the small number of <xref linkend="guc-num-init-children">,
the serialize accept can degrade the performance because of
<note>
<para>
<!--
- It is recomended to do a benchmark before deciding wether to use
+ It is recommended to do a benchmark before deciding wether to use
<varname>serialize_accept</varname> or not, because the corelation
of <xref linkend="guc-num-init-children"> and <varname>serialize_accept</varname>
can be different on different environments.
with information outlined below.
All unrecognized escapes are ignored. Other characters are copied straight to
the log line. Default is '%t: pid %p: ', which prints timestamp and process id,
- which keeps backward compatib
ily with pre<productname>Pgpool-II</productname>
+ which keeps backward compatibly with pre<productname>Pgpool-II</productname>
<emphasis>V3.4</emphasis>.
-->
これは、各ログ行の先頭に出力する<function>printf</>の書式文字列です。
</row>
<row>
- <entry>watchdog heart beat reciever</entry>
+ <entry>watchdog heart beat receiver</entry>
<entry>heart_beat_receiver</entry>
</row>
<!--
<productname>Pgpool-II</productname> <emphasis>V2.2</emphasis> or later,
automatically detects whether the table has a SERIAL columns or not,
- so it never locks the table if it desn't have the SERIAL columns.
+ so it never locks the table if it doesn't have the SERIAL columns.
-->
<productname>Pgpool-II</productname> <emphasis>V2.2</emphasis>以降では、テーブルがSERIAL列を持つかどうか自動判別するため、SERIAL列がなければ決してテーブルをロックしません。
</para>
<para>
<!--
<varname>backend_weight</varname> specifies the load balance
- ratio of the backends. It may be set to any interger or
- floating point value greater than or equeal zero.
+ ratio of the backends. It may be set to any integer or
+ floating point value greater than or equal zero.
Multiple backends can be specified by
adding a number at the end of the parameter name
(e.g. backend_weight0). If you plan to use only one
reloading a configuration file. However, this will take
effect only for new established client sessions.
<productname>Pgpool-II</> <emphasis>V2.2.6</>, <emphasis>V2.3</> or later
- allows alllow updating the values by reloading a configuration file.
+ allows allow updating the values by reloading a configuration file.
This is useful if you want to prevent any query sent to
standbys to perform some administrative work in native replication mode.
-->
<row>
<entry><literal>DISALLOW_TO_FAILOVER</literal></entry>
<!--
- <entry>Disllow to failover or detaching backend
+ <entry>Disallow to failover or detaching backend
This is useful when you protect backend by
using HA (High Availability) softwares such as
<productname>Heartbeat</> or <productname>Pacemaker</>. You cannot specify with
Set <xref linkend="guc-sr-check-period"> to 0 to
disable streaming replication delay checking. This
is because <productname>Aurora</productname> does
- not provide neccessary functions to check the
+ not provide necessary functions to check the
replication delay.
-->
<xref linkend="guc-sr-check-period">を0にして、ストリーミングレプリケーション遅延チェックを無効にします。
Pgpool-IIには定期的にPostgreSQLを状態をチェックし、
障害を検知するとフェイルオーバさせる機能はありますが、Kubernetesでは、
PostgreSQLの状態はKubernetesによって管理されるので、
- Pgpoo-IIの自動フェイルオーバ機能を無効にします。
+ Pgpool-IIの自動フェイルオーバ機能を無効にします。
</para>
<para>
また、<productname>PostgreSQL</productname> Podが再作成されたり、
</programlisting>
<para>
しかし、Kubernetes環境では、Pgpool-IIはすべてのレプリカに接続するのではなく、
- レプリカSerivceを経由して、いずれかのレプリカに接続します。
+ レプリカServiceを経由して、いずれかのレプリカに接続します。
レプリカが複数存在しても、Pgpool-IIが1台のレプリカとして管理しています。
そのため、レプリカServiceにぶら下がっている複数のレプリカのうち、
どのレプリカが遅延しているのかはPgpool-IIが正確に判断できません。
</programlisting>
<!--
<productname>Pgpool-II</productname> only accepts connections from the localhost
- using port 9999 by the default. If you wish to receive conenctions from other hosts,
+ using port 9999 by the default. If you wish to receive connections from other hosts,
set <xref linkend="guc-listen-addresses"> to <literal>'*'</literal>.
-->
<productname>Pgpool-II</> はデフォルトではローカルホストからのポート番号9999への接続のみを受け付けます。
for each server. If the servers are placed on separate machines,
they must be configured properly so that they can accept network
connections from <productname>Pgpool-II</productname>.
- In this exa
pmle, we create 3 <productname>PostgreSQL</productname> servers and
+ In this exa
mple, we create 3 <productname>PostgreSQL</productname> servers and
specify the PostgreSQL information in the following parameters.
-->
次に、<productname>Pgpool-II</productname>のための<productname>PostgreSQL</>サーバを設定する必要があります。
オンラインリカバリで実行される<function>pgpool_recovery</function>関数は
<productname>PostgreSQL</productname>のスーパーユーザ権限が必要なため、
<varname>recovery_user</varname>に<emphasis>スーパーユーザ</emphasis>を指定しなければなりません。
- ここでは、<literal>postrges</literal>ユーザを指定します。
+ ここでは、<literal>postgres</literal>ユーザを指定します。
</para>
<programlisting>
recovery_user = 'postgres'
<application>Watchdog</application>死活監視の設定では、
死活監視の方法を指定する<xref linkend="guc-wd-lifecheck-method">、
監視間隔(秒)を指定する<xref linkend="guc-wd-interval">を設定します。
- この設定例では、死活監視の方法は<literal>hearbeat</literal>を用います。
+ この設定例では、死活監視の方法は<literal>heartbeat</literal>を用います。
</para>
<programlisting>
オンラインリカバリで実行される<function>pgpool_recovery</function>関数は
<productname>PostgreSQL</productname>のスーパーユーザ権限が必要なため、
<varname>recovery_user</varname>に<emphasis>スーパーユーザ</emphasis>を指定しなければなりません。
- ここでは、<literal>postrges</literal>ユーザを指定します。
+ ここでは、<literal>postgres</literal>ユーザを指定します。
</para>
<programlisting>
recovery_user = 'postgres'
<!--
Specifies a user command to run when a <productname>PostgreSQL</> backend node gets detached.
<productname>Pgpool-II</productname> replaces the following special characters
- with the backend specific information before excuting the command.
+ with the backend specific information before executing the command.
-->
<productname>PostgreSQL</>バックエンドノードが切り離される時に実行するユーザコマンドを指定します。
<productname>Pgpool-II</productname>はコマンド実行の前に、以下の特殊文字をバックエンドの具体的な情報に置き換えます。
Specifies a user command to run when a <productname>PostgreSQL</> backend node gets attached to
<productname>Pgpool-II</productname>. <productname>Pgpool-II</productname>
replaces the following special characters with the backend specific information.
- before excuting the command.
+ before executing the command.
-->
<productname>PostgreSQL</>バックエンドノードが<productname>Pgpool-II</productname>に復帰された時に実行するユーザコマンドを指定します。
<productname>Pgpool-II</productname>はコマンド実行の前に、以下の特殊文字をバックエンドの具体的な情報に置き換えます。
<para>
<!--
<productname>Pgpool-II</productname> replaces the following special characters
- with the backend specific information before excuting the command.
+ with the backend specific information before executing the command.
-->
<productname>Pgpool-II</productname>はコマンド実行の前に、以下の特殊文字をバックエンドの具体的な情報に置き換えます。
<!--
When set to on, standby node be automatically failback, if the node status
is down but streaming replication works normally. This is useful when
- standby node is degenerated by pgpool because of the tempolary network failure.
+ standby node is degenerated by pgpool because of the temporary network failure.
-->
onに設定した場合、ストリーミングレプリケーションが正常に動作しており、かつバックエンドノードのステータスがダウンのとき、スタンバイノードを自動で復帰させることができます。
これは、一時的なネットワーク障害などによりスタンバイノードが認識できず縮退が行われた場合などに役立ちます。
<para>
<!--
<xref linkend="guc-auto-failback"> may not work, when replication slot is used.
- There’s possibility that the streaming replication is stopped, bacause
+ There’s possibility that the streaming replication is stopped, because
<xref linkend="guc-failover-command"> is executed and replication slot is deleted by
the command.
-->
made between <productname>Pgpool</productname>
and <productname>Pgpool-II</productname> was that the project was
changed from a personal project to a group project owned by the
- Pgpool Developement Group.
+ Pgpool Development Group.
-->
2006年、<productname>Pgpool</productname>は<productname>Pgpool-II</productname>となりました。
最初の1.0リリースでは、<productname>Pgpool</productname>の多くの制限事項が撤廃されました。
たとえば、<productname>PostgreSQL</productname>サーバ数は2まで、といった制限です。
また、パラレルクエリやPCPコマンド（PCPは、"Pgpool Control Protocol"の略です）といった多くの機能が追加されました。
- <productname>Pgpool</productname>から<productname>Pgpool-II</productname>への一番重要な変更は、おそらく個人プロジェクトから、Pgpool Developement Groupが所有するグループプロジェクトになったことでした。
+ <productname>Pgpool</productname>から<productname>Pgpool-II</productname>への一番重要な変更は、おそらく個人プロジェクトから、Pgpool Development Groupが所有するグループプロジェクトになったことでした。
</para>
</sect1>
<!--
<productname>Pgpool-II</productname> need function of <function>pgpool_recovery</function>,
<function>pgpool_remote_start</function> and <function>pgpool_switch_xlog</function>,
- when you use the online recovery that discribes latter.
+ when you use the online recovery that describes latter.
Also pgpoolAdmin of management tool, stop, restart or reload a
- <productname>PostgreSQL </prodcutname> on the screen by use <function>pgpool_pgctl<function>.
- It is enough, if these function installed in template1 fisrt. These
+ <productname>PostgreSQL </productname> on the screen by use <function>pgpool_pgctl<function>.
+ It is enough, if these function installed in template1 first. These
function do not needed that install in all databases.
-->
後述の オンラインリカバリ の機能を使う場合には、 pgpool_recovery, pgpool_remote_start, pgpool_switch_xlog という関数が必要です。
as this template database will be cloned to create new databases.
-->
<command>CREATE EXTENSION</command>または<filename>pgpool-regclass.sql</filename>の実行は、<productname>Pgpool-II</productname>経由でアクセスされる全てのデータベースで実行しなければなりません。
- ただし、<command>CREATE EXTENSINON</command>または"psql -f pgpool-regclass.sql template1"の実行後に作成されたデータベースでは、新しいデータベース作成のためにテンプレートデータベースが複製されるため、これを実行する必要はありません。
+ ただし、<command>CREATE EXTENSION</command>または"psql -f pgpool-regclass.sql template1"の実行後に作成されたデータベースでは、新しいデータベース作成のためにテンプレートデータベースが複製されるため、これを実行する必要はありません。
</para>
</sect1>
<firstterm>pool</firstterm> of
<productname>PostgreSQL</productname> servers to achieve some
features that are not available with single
- <productname>PostgreSQL</productname> installation. The fearures
+ <productname>PostgreSQL</productname> installation. The features
include:
-->
<productname>Pgpool-II</productname>は<productname>PostgreSQL</productname>の<firstterm>pool</firstterm>を管理することによって、単一の<productname>PostgreSQL</productname>構成では得られない以下のような機能を提供します。
offers an HA feature for <productname>Pgpool-II</productname>
itself, called <firstterm>Watchdog</firstterm> (see <xref
linkend="tutorial-watchdog"> for more details). Moreover
- <productname>Pgpool-II</productname> hires sophoiscated
- <firstterm>quorum</firstterm> algorithm to aovid false positive
+ <productname>Pgpool-II</productname> hires sophisticated
+ <firstterm>quorum</firstterm> algorithm to avoid false positive
errors and split brain problem to make the whole HA system
highly reliable. See <xref
linkend="config-watchdog-failover-behavior"> for more details.
</programlisting>
<para>
<!--
- If you want to use comments without supressing load balancing, you can set
+ If you want to use comments without suppressing load balancing, you can set
<xref linkend="guc-allow-sql-comments"> to on.
Please refer to <xref linkend="guc-replicate-select"> as well.
-->
<!--
The JDBC driver has an autocommit option. If the autocommit is false,
the JDBC driver sends "BEGIN" and "COMMIT" by itself, and an explicit
- tranasacttion starts. In this case the same restriction above regarding
+ transaction starts. In this case the same restriction above regarding
load balancing will be applied.
-->
JDBC ドライバにはautocommitオプションがあります。
<para>
<!--
- If writing queires appear, succeeding read queries may not be
+ If writing queries appear, succeeding read queries may not be
load balanced. i.e. sent to primary node (in streaming
replication mode) or main node (in other mode) depending on the
setting of <xref linkend="guc-disable-load-balance-on-write">.
</para>
</sect2>
- <sect2 id="runtime-config-load-balancing-in-streaming-raplication">
+ <sect2 id="runtime-config-load-balancing-in-streaming-replication">
<!--
<title>Load Balancing in Streaming Replication</title>
<para>
<!--
The "Application name" is a name specified by a client when it connects to database,
- and is avalable in <productname>PostgreSQL</> <emphasis>V9.0</> or later.
+ and is ava
ilable in <productname>PostgreSQL</> <emphasis>V9.0</> or later.
-->
「アプリケーション名」とはクライアントがデータベースに接続する時に指定する名称で、<productname>PostgreSQL</> <emphasis>V9.0</>以降で利用可能です。
</para>
<para>
<!--
- To prevent load balancing of READ dependent objects, you may specificy the object name
+ To prevent load balancing of READ dependent objects, you may specify the object name
followed by a colon(<literal>:</>) and then a comma(<literal>,</>) separated list of dependent object names.
<replaceable>"[object]:[dependent-object]"</replaceable>
In an explicit transaction block after a WRITE statement has been issues, this will prevent
<para>
<!--
- <varname>memqcache_cache_block_size</varname> must be set to atleast 512.
+ <varname>memqcache_cache_block_size</varname> must be set to at least 512.
-->
<varname>memqcache_cache_block_size</varname>は、512以上の値でなければなりません。
</para>
Specifies the relation cache expiration time in seconds.
The relation cache is used for caching the query result of
<productname>PostgreSQL</> system catalogs that is used by <productname>Pgpool-II
- </productname> to get various informations including the table
+ </productname> to get various information including the table
structures and to check table types(e.g. To check if the referred
table is a temporary table or not). The cache is maintained in
the local memory space of <productname>Pgpool-II</productname>
For online recovery, the recovery target node must be in detached
state. This means the node must be either manually detached by
<xref linkend="pcp-detach-node"> or automatically detached
- by <productname>Pgpool-II</productname> as a consequnece of
+ by <productname>Pgpool-II</productname> as a consequence of
failover.
-->
オンラインリカバリを実施するためには、リカバリ対象のノードは<productname>Pgpool-II</productname>から切り離された状態になっていなければなりません。
</para>
<para>
<!--
- Connections from cliens are not allowd only in the second stage
- while the data can be updated or retrieved during the first statge.
+ Connections from clients are not allowed only in the second stage
+ while the data can be updated or retrieved during the first stage.
-->
ファーストステージではデータの更新や読み取りができますが、セカンドステージではクライアントからの接続は許されていません。
</para>
<!--
Specifies the <productname>PostgreSQL</> user name to perform online recovery.
<varname>recovery_user</varname> must specify superuser,
- beacause <function>pgpool_recovery</function> function is executed
+ because <function>pgpool_recovery</function> function is executed
during online recovery, require superuser privilege.
-->
オンラインリカバリを行うための<productname>PostgreSQL</>ユーザ名です。
database cluster directory for security reasons.
For example, if <varname>recovery_1st_stage_command</varname> = <literal>
'sync-command'</literal>, then <productname>Pgpool-II</productname> will
- look for the command scrit in <literal>$PGDATA</literal> directory and will
+ look for the command script in <literal>$PGDATA</literal> directory and will
try to execute <command>$PGDATA/sync-command</command>.
-->
オンラインリカバリのファーストステージでメイン（プライマリ）ノードで実行されるコマンドを指定します。
database cluster directory for security reasons.
For example, if <varname>recovery_2nd_stage_command</varname> = <literal>
'sync-command'</literal>, then <productname>Pgpool-II</productname> will
- look for the command scrit in <literal>$PGDATA</literal> directory and will
+ look for the command script in <literal>$PGDATA</literal> directory and will
try to execute <command>$PGDATA/sync-command</command>.
-->
オンラインリカバリのセカンドステージでメインノードで実行されるコマンドを指定します。
この問題に対処するための方法がいくつかあります。
</para>
- <sect2 id="controling-num-init-children">
+ <sect2 id="controlling-num-init-children">
<title>num_init_childrenの調整</title>
<para>
この問題に対処するための明らかな方法は、子プロセスの数を増やすことです。
</para>
</sect2>
- <sect2 id="controling-listen-backlog-multiplier">
+ <sect2 id="controlling-listen-backlog-multiplier">
<title>listen_backlog_multiplierの制御</title>
<para>
別な解決方法は、接続要求待ち行列を長くすることです。
<refname>pcp_detach_node</refname>
<refpurpose>
<!--
- detaches the given node from Pgpool-II. Exisiting connections to Pgpool-II are forced to be disconnected.</refpurpose>
+ detaches the given node from Pgpool-II. Existing connections to Pgpool-II are forced to be disconnected.</refpurpose>
-->
<productname>Pgpool-II</productname> からノードを切り離す</refpurpose>
</refnamediv>
<listitem>
<para>
<!--
- Display all backend nodes informatio.
+ Display all backend nodes information.
-->
すべてのバックエンドノードの情報を表示します。
</para>
</para>
<para>
<!--
- If ommitted then gets information of all watchdog nodes.
+ If omitted then gets information of all watchdog nodes.
-->
省略された場合は、全ての watchdog ノードの情報を取得します。
</para>
<para>
<!--
Set the path to the <filename>.pgpoolkey</filename> file.
- Mandatory if you use AES256 encrypted password and the file is placed other than the standard locatiaon and used.
+ Mandatory if you use AES256 encrypted password and the file is placed other than the standard location and used.
-->
<filename>.pgpoolkey</filename>ファイルへのパスを指定します。
AES256暗号化パスワードを使用し、このファイルが標準の場所以外にある場合には必須です。
<!--
Reload configuration file
of <productname>Pgpool-II</productname>. No specific options
- exist for realod mode. Common options are applicable.
+ exist for reload mode. Common options are applicable.
-->
<productname>Pgpool-II</productname>の設定ファイルを再読み込みします。
reloadモードには専用のオプションはありません。
<partintro>
<para>
<!--
- This part contains reference information for the pgool-II.
+ This part contains reference information for the pgpool-II.
-->
ここには <productname>Pgpool-II</productname> のリファレンス情報があります。
</para>
to <productname>PostgreSQL</productname> with the result
(3). <productname>PostgreSQL</productname> returns the result
to <productname>Pgpool-II</productname> (5)
- and <productname>Pgpool-II</productname> fowards the data to
+ and <productname>Pgpool-II</productname> forwards the data to
the user (6).
-->
<productname>Pgpool-II</productname>経由でも(1)、あるいは直接<productname>PostgreSQL</productname>に対しても(2)、関数を呼び出すことができます。
of <productname>PostgreSQL</productname>. The pcp port number
is hard coded as 9898, the pcp user name is assumes to be same
as caller's <productname>PostgreSQL</productname> user name.
- password is extraced from $HOME/.pcppass.
+ password is extracted from $HOME/.pcppass.
-->
2番目の形式では、<productname>Pgpool-II</productname>サーバ名が必要になります。
サーバ名は<productname>PostgreSQL</productname>の"CREATE FOREIGN SERVER"コマンドで定義済みでなければなりません。
<para>
<!--
Allow to choose the least replication delay standby node when
- selecting the load balance node. For this pupose a new
+ selecting the load balance node. For this purpose a new
parameter <xref linkend="guc-prefer-lower-delay-standby"> is
added.
-->
<listitem>
<para>
<!--
- Support include directive in <filename>pgppol.conf</filename>
+ Support include directive in <filename>pgpool.conf</filename>
file. You can have separate sub-config file to be included in
<filename>pgpool.conf</filename>.
-->
<para>
<!--
- This section descibes current restrictions of <productname>Pgpool-II</productname>.
+ This section desc
ribes current restrictions of <productname>Pgpool-II</productname>.
-->
この章では、<productname>Pgpool-II</productname>の現在の制限事項について説明します。
<!--
In the replication mode or native replication mode, trust and pam methods are supported. md5 is also
supported since <productname>Pgpool-II</productname> 3.0. md5
- is supported by using an authencitaion file <filename>pool_passwd</filename>.
+ is supported by using an authentication file <filename>pool_passwd</filename>.
scram-sha-256, cert, and clear text password is also supported since
<productname>Pgpool-II</productname> 4.0.
<filename>pool_passwd</filename> is default name of the
<listitem>
<para>
<!--
- <productname>Pgpool-II</productname> does not perform encoding converion between client and
+ <productname>Pgpool-II</productname> does not perform encoding conversion between client and
<productname>PostgreSQL</productname> for multi-byte characters.
The encoding for the client and backends must be the same.
-->
<!-- doc/src/sgml/config.sgml -->
<sect1 id="runtime-ssl">
- <title>Secure Sockect Layer (SSL)</title>
+ <title>Secure Socket Layer (SSL)</title>
<sect2 id="runtime-ssl-settings">
<!--
Before going further, you should properly set
up <filename>pgpool.conf</filename> with streaming replication
- mode. Sample configulations are provided with
+ mode. Sample configurations are provided with
<productname>Pgpool-II</productname>, there configuration file
are located at /usr/local/etc with default installation from
source code. you can copy
installation. The argument -p is to specify the port number
assigned to the command, which is 11001 set
by <command>pgpool_setup</command>. The argument -n is to
- specify the node id to be receovered. After executing the command,
+ specify the node id to be recovered. After executing the command,
node 0 returned to "up" status.
-->
<xref linkend="pcp-recovery-node">は、インストールされた<productname>Pgpool-II</productname>に含まれる管理コマンドの一つです。
<para>
<figure>
<!--
- <title>Process architecure of <productname>Pgpool-II</productname></title>
+ <title>Process architec
ture of <productname>Pgpool-II</productname></title>
-->
<title><productname>Pgpool-II</productname>のプロセス構造</title>
<mediaobject>
Specifies the authentication key used for all watchdog communications.
All <productname>Pgpool-II</productname> must have the same key.
Packets from watchdog having different key will get rejected.
- This authentication is also applied to the heatrbeat singals
+ This authentication is also applied to the heartbeat signals
when the <literal>heartbeat</> mode is used as a lifecheck method.
-->
- wachdog間通信で用いられる認証キーを指定します。
+ watchdog間通信で用いられる認証キーを指定します。
全ての<productname>Pgpool-II</productname>で同じキーを指定する必要があります。
認証キーが異なるwatchdogからの通信は拒絶されます。
死活監視を<literal>heartbeat</>モードで行う場合には、この認証はハートビート信号にも適用されます。
<sect2 id="config-watchdog-escalation-de-escalation">
<!--
- <title>Behaivor on escalation and de-escalation</title>
+ <title>Behavior on escalation and de-escalation</title>
-->
<title>昇格および降格時の振る舞い</title>
<para>
<para>
<!--
When set to on, watchdog clears all the query cache in the shared memory
- when pgpool-II escaltes to active. This prevents the new active <productname>Pgpool-II</productname>
- from using old query caches inconsistence to the old active.
+ when pgpool-II escal
ates to active. This prevents the new active <productname>Pgpool-II</productname>
+ from using old query caches inconsistences to the old active.
-->
このオプションがonの場合、pgpool-II がアクティブに昇格した時に、共有メモリ上のクエリキャッシュを全て削除します。
これにより、新しいアクティブの<productname>Pgpool-II</productname>が旧アクティブと非整合な古いクエリキャッシュを使うことを防止します。
</para>
<para>
<!--
- <literal>heartbeat</literal>: In this mode, watchdog sends the heartbeat si
ngals (<acronym>UDP</acronym> packets)
+ <literal>heartbeat</literal>: In this mode, watchdog sends the heartbeat si
gnals (<acronym>UDP</acronym> packets)
periodically to other <productname>Pgpool-II</productname>. Similarly watchdog also receives the signals
from other <productname>Pgpool-II</productname> .
If there are no signal for a certain period, watchdog regards is as failure
<!--
Specifies the <acronym>IP</acronym> address or <acronym>hostname</acronym> of
for sending and receiving the heartbeat signals.
- Multiple destinations can be configured for the heartbeat singnals,
+ Multiple destinations can be configured for the heartbeat signals,
the number at the end of the parameter name is
referred as the "pgpool node id", that starts from 0.
-->
<para>
<!--
Specifies the port number for sending the heartbeat signals.
- Multiple destinations can be configured for the heartbeat singnals,
+ Multiple destinations can be configured for the heartbeat signals,
the number at the end of the parameter name is
referred as the "pgpool node id", that starts from 0.
-->
If <productname>PostgreSQL</productname> is listening on 11002
port, rather than the standard 5432 port, you can do:
<programlisting>
- firewall-cmd --zone=public --remove-service=popstgresql --permanent
+ firewall-cmd --zone=public --remove-service=postgresql --permanent
firewall-cmd --zone=public --add-port=11002/tcp --permanent
firewall-cmd --reload
</programlisting>
<para>
You can avoid maintaining <filename>pool_passwd</filename> by
using <xref linkend="guc-allow-clear-text-frontend-auth"> as well
- but it does not enfornce to use SSL encryption because
+ but it does not enforce to use SSL encryption because
<filename>pool_hba.conf</filename> cannot be used with the
parameter.
</para>
Because failover is managed by <productname>Kubernetes</productname>,
specify <literal>DISALLOW_TO_FAILOVER</literal> flag to <xref linkend="GUC-BACKEND-FLAG">
for both of the two nodes and <literal>ALWAYS_PRIMARY</literal> flag to <xref linkend="GUC-BACKEND-FLAG">0.
- The setiing of <xref linkend="GUC-BACKEND-DATA-DIRECTORY"> is not required.
+ The setting of <xref linkend="GUC-BACKEND-DATA-DIRECTORY"> is not required.
</para>
<para>
For example, the following environment variables defined in manifest,
On Kubernetes, Kubernetes monitors the PostgreSQL pods,
if a pod goes down, Kubernetes will restart a new one.
You need to disable Pgpool-II's automated failover,
- becuase Pgpool-II's automated failover is not required on Kubernetes.
+ because Pgpool-II's automated failover is not required on Kubernetes.
</para>
<para>
Specify PostgreSQL node 0 as primary (<literal>ALWAYS_PRIMARY</literal>),
because Service name doesn't change even if the primary or replica pod
- is sacled, restarted or failover occurred.
+ is scaled, restarted or failover occurred.
</para>
<programlisting>
backend_flag0 ='ALWAYS_PRIMARY|DISALLOW_TO_FAILOVER'
<para>
Define the environment variables using Secret is the recommended way to keep user credentials secure.
In most PostgreSQL Operators, several Secrets which define the
- <productname>PostgreSQL</productname> user's redentials will be automaticlly
+ <productname>PostgreSQL</productname> user's credentials will be automatically
created when creating a PostgreSQL cluster.
Use <command>kubectl get secret</command> command to check the existing Secrets.
</para>
specified in <varname>sr_check_user</varname> and configure the
environment variables to reference the created Secret.
In most PostgreSQL Operators, several secrets which define the
- <productname>PostgreSQL</productname> user's redentials will be automaticlly
+ <productname>PostgreSQL</productname> user's credentials will be automatically
created when creating a PostgreSQL cluster.
Use <command>kubectl get secret</command> command to check the existing secrets.
</para>
for each server. If the servers are placed on separate machines,
they must be configured properly so that they can accept network
connections from <productname>Pgpool-II</productname>.
- In this exa
pmle, we create 3 <productname>PostgreSQL</productname> servers and
+ In this exa
mple, we create 3 <productname>PostgreSQL</productname> servers and
specify the PostgreSQL information in the following parameters.
<programlisting>
replication.
</para>
<para>
- In thie example we use 3 servers with CentOS 7.9 installed.
+ In this example we use 3 servers with CentOS 7.9 installed.
Let these servers be <literal>server1</literal>,
<literal>server2</literal>, <literal>server3</literal>.
We install <productname>PostgreSQL</productname> on all servers and
<para>
To use the online recovery of <productname>Pgpool-II</productname>,
the settings that allow <emphasis>passwordless</emphasis> SSH to all
- servers are requried.
+ servers are required.
Execute the following command on all servers to set up passwordless
<literal>SSH</literal>.
The generated key file name is <literal>id_rsa_pgpool</literal>.
If <productname>PostgreSQL</productname> is listening on 11002
port, rather than the standard 5432 port, you can do:
<programlisting>
- firewall-cmd --zone=public --remove-service=popstgresql --permanent
+ firewall-cmd --zone=public --remove-service=postgresql --permanent
firewall-cmd --zone=public --add-port=11002/tcp --permanent
firewall-cmd --reload
</programlisting>
<firstterm>pool</firstterm> of
<productname>PostgreSQL</productname> servers to achieve some
features that are not available with single
- <productname>PostgreSQL</productname> installation. The fearures
+ <productname>PostgreSQL</productname> installation. The features
include:
<variablelist>
offers an HA feature for <productname>Pgpool-II</productname>
itself, called <firstterm>Watchdog</firstterm> (see <xref
linkend="tutorial-watchdog"> for more details). Moreover
- <productname>Pgpool-II</productname> hires sophoiscated
- <firstterm>quorum</firstterm> algorithm to aovid false positive
+ <productname>Pgpool-II</productname> hires sophisticated
+ <firstterm>quorum</firstterm> algorithm to avoid false positive
errors and split brain problem to make the whole HA system
highly reliable. See <xref
linkend="config-watchdog-failover-behavior"> for more details.
In memory query cache can be used with all modes of
<productname>Pgpool-II</productname>.
The in memory query cache keeps the SELECT results and the results are reused.
- When the underlying table gets updated, corresponding cache enrties are deleted (in case <xref linkend="guc-memqcache-auto-cache-invalidation"> is on. This parameter is on by default), thus restarting <productname>Pgpool-II</productname> is not neccessary.
+ When the underlying table gets updated, corresponding cache entries are deleted (in case <xref linkend="guc-memqcache-auto-cache-invalidation"> is on. This parameter is on by default), thus restarting <productname>Pgpool-II</productname> is not necessary.
</para>
<para>
In memory cache saves the pair of SELECT statement
<para>
A <literal>SELECT</literal> result is basically registered when
- SELECT normaly finishes. If an explicit transaction is executing,
+ SELECT normally finishes. If an explicit transaction is executing,
<literal>SELECT</literal> result is not registered until the
transaction is committed. Also in extended query mode, the timing
- of cache registeration varies depending on <link
+ of cache registration varies depending on <link
linkend="guc-backend-clustering-mode">clustering mode</link>. In
<link linkend="runtime-config-streaming-replication-mode">streaming
replication mode</link> and <link
This feature is particularly useful for
testing <xref linkend="guc-failover-require-consensus">. Suppose
we have 3 watchdog node. Each watchdog checks healthiness of
- backend 0. By setting "0 down" in the file onky under watchdog 0,
+ backend 0. By setting "0 down" in the file only under watchdog 0,
other watchdogs disagree with the unhealthiness of backend 0, so
failover will not occur. This kind of partial network failure can
be simulated using this feature.
<refnamediv>
<refname>pcp_detach_node</refname>
<refpurpose>
- detaches the given node from Pgpool-II. Exisiting connections to Pgpool-II are forced to be disconnected.</refpurpose>
+ detaches the given node from Pgpool-II. Existing connections to Pgpool-II are forced to be disconnected.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<term><option>--all</option></term>
<listitem>
<para>
- Display all backend nodes informatio.
+ Display all backend nodes information.
</para>
</listitem>
</varlistentry>
<listitem>
<para>
Allow to choose the least replication delay standby node when
- selecting the load balance node. For this pupose a new
+ selecting the load balance node. For this purpose a new
parameter <xref linkend="guc-prefer-lower-delay-standby"> is
added.
</para>
<listitem>
<para>
- Support include directive in <filename>pgppol.conf</filename>
+ Support include directive in <filename>pgpool.conf</filename>
file. You can have separate sub-config file to be included in
<filename>pgpool.conf</filename>.
</para>
projects / pgpool2.git / commitdiff