pgpool2.git / summary / log / commit / refs
commit c3312d88a32dbd49e7e24eaee9cc8bdc7b422f0b
Author: Bo Peng <pengbo@sraoss.co.jp>
Date: Thu Jun 20 03:53:40 2019 +0000
doc: Fix documentation typos.
doc/src/sgml/connection-pooling.sgml | 2 +-
doc/src/sgml/connection-settings.sgml | 6 +++---
doc/src/sgml/examples.sgml | 6 +++---
doc/src/sgml/failover.sgml | 6 +++---
doc/src/sgml/history.sgml | 2 +-
doc/src/sgml/intro.sgml | 4 ++--
doc/src/sgml/loadbalance.sgml | 14 +++++++-------
doc/src/sgml/misc-config.sgml | 2 +-
doc/src/sgml/online-recovery.sgml | 12 ++++++------
doc/src/sgml/performance.sgml | 8 ++++----
doc/src/sgml/release-4.0.sgml | 8 ++++----
doc/src/sgml/restrictions.sgml | 6 +++---
doc/src/sgml/runtime.sgml | 8 ++++----
doc/src/sgml/watchdog.sgml | 8 ++++----
14 files changed, 46 insertions(+), 46 deletions(-)
diff --git a/doc/src/sgml/connection-pooling.sgml b/doc/src/sgml/connection-pooling.sgml
index 5106e2d84..cd084243c 100644
--- a/doc/src/sgml/connection-pooling.sgml
+++ b/doc/src/sgml/connection-pooling.sgml
@@ -650,7 +650,7 @@ local0.* /var/log/pgpool.log
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 compatibily with pre<productname>Pgpool-II</productname>
+ which keeps backward compatibility with pre<productname>Pgpool-II</productname>
<emphasis>V3.4</emphasis>.
</para>
diff --git a/doc/src/sgml/connection-settings.sgml b/doc/src/sgml/connection-settings.sgml
index 569bca552..8ec80afe6 100644
--- a/doc/src/sgml/connection-settings.sgml
+++ b/doc/src/sgml/connection-settings.sgml
@@ -1047,7 +1047,7 @@
<listitem>
<para>
<varname>backend_weight</varname> specifies the load balance
- ratio of the backends. It may be set to any interger or
+ ratio of the backends. It may be set to any integer or
floating point value greater than or equal to zero.
Multiple backends can be specified by
adding a number at the end of the parameter name
@@ -1059,7 +1059,7 @@
reloading a configuration file. However, this will take
effect only for new established client sessions.
<productname>Pgpool-II</productname> <emphasis>V2.2.6</emphasis>, <emphasis>V2.3</emphasis>
- or later allows alllow updating the values by reloading a
+ or later allows updating the values by reloading a
configuration file. This is useful if you want to prevent
any query sent to slaves to perform some administrative
work in master/slave mode.
@@ -1140,7 +1140,7 @@
</row>
<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</productname>
diff --git a/doc/src/sgml/examples.sgml b/doc/src/sgml/examples.sgml
index 5fea966f8..ac66844d9 100644
--- a/doc/src/sgml/examples.sgml
+++ b/doc/src/sgml/examples.sgml
@@ -1052,7 +1052,7 @@ To allow Pgpool-II to accept all incoming connections, we set <varname>listen_ad
listen_addresses = '*'
</programlisting>
<para>
-Specifiy replication delay check user and password. In this example, we leave
+Specify replication delay check user and password. In this example, we leave
<xref linkend="GUC-SR-CHECK-USER"> empty, and create the entry in <xref linkend="GUC-POOL-PASSWD">.
From <productname>Pgpool-II</productname> 4.0, if these parameters are left blank,
<productname>Pgpool-II</productname> will first try to get the password for that
@@ -1064,7 +1064,7 @@ sr_check_user = 'pgpool'
sr_check_password = ''
</programlisting>
<para>
-Enable health check so that pgpool-II performs failover. Also, if the network is unstable,
+Enable health check so that <productname>Pgpool-II</> performs failover. Also, if the network is unstable,
the health check fails even though the backend is running properly, failover or degenerate operation may occur.
In order to prevent such incorrect detection of health check, we set <varname>health_check_max_retries = 3</varname>.
Specify <xref linkend="GUC-HEALTH-CHECK-USER"> and <xref linkend="GUC-HEALTH-CHECK-PASSWORD"> in the same way like <xref linkend="GUC-SR-CHECK-USER"> and <xref linkend="GUC-SR-CHECK-PASSWORD">.
@@ -1428,7 +1428,7 @@ Because in the section <link linkend="EXAMPLE-CLUSTER-PRE-SETUP">Before Starting
we already set <productname>PostgreSQL</productname> authentication method to
<acronym>scram-sha-256</acronym>, it is necessary to set a client authentication by
<productname>Pgpool-II</productname> to connect to backend nodes.
-Please note that only AES encrypted password or clear text passowrd can be specified
+Please note that only AES encrypted password or clear text password can be specified
in <xref linkend="guc-health-check-password">, <xref linkend="guc-sr-check-password">,
<xref linkend="guc-wd-lifecheck-password">, <xref linkend="guc-recovery-password"> in <filename>pgpool.conf</filename>.
When installing with RPM,
diff --git a/doc/src/sgml/failover.sgml b/doc/src/sgml/failover.sgml
index a78eae11f..5c96496c6 100644
--- a/doc/src/sgml/failover.sgml
+++ b/doc/src/sgml/failover.sgml
@@ -174,7 +174,7 @@
<note>
<para>
- The "master node" referes to a node which has the
+ The "master node" refers to a node which has the
"youngest (or the smallest) node id" among live the
database nodes. In <link linkend="running-mode">streaming
replication mode</link>, this may be different from
@@ -359,7 +359,7 @@ for each backend node
{
if (the node is not the new primary)
set down node status to shared memory status
- memorize that folllow master command is needed to execute
+ memorize that follow master command is needed to execute
}
if (we need to executed follow master command)
fork a child process
@@ -373,7 +373,7 @@ if (we need to executed follow master command)
<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.
</para>
<table id="follow-master-command-table">
diff --git a/doc/src/sgml/history.sgml b/doc/src/sgml/history.sgml
index 5ce15421e..47da578f1 100644
--- a/doc/src/sgml/history.sgml
+++ b/doc/src/sgml/history.sgml
@@ -33,6 +33,6 @@
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.
</para>
</sect1>
diff --git a/doc/src/sgml/intro.sgml b/doc/src/sgml/intro.sgml
index f1b563ea2..0111162e4 100644
--- a/doc/src/sgml/intro.sgml
+++ b/doc/src/sgml/intro.sgml
@@ -118,9 +118,9 @@
<term>Automated fail over</term>
<listitem>
<para>
- If one of database servers goes down or becomes unrechable,
+ If one of database servers goes down or becomes unreachable,
<productname>Pgpool-II</productname> will detaches it and continues operations using rest
- of database servers. There are some sophiscated features which
+ of database servers. There are some sophisticated features which
help the automated fail over including timeout and retries.
</para>
</listitem>
diff --git a/doc/src/sgml/loadbalance.sgml b/doc/src/sgml/loadbalance.sgml
index bd6e05f68..ad49f3779 100644
--- a/doc/src/sgml/loadbalance.sgml
+++ b/doc/src/sgml/loadbalance.sgml
@@ -8,7 +8,7 @@
works with Master Slave mode (<xref linkend="runtime-config-master-slave-mode">)
and Replication mode (<xref linkend="runtime-config-replication-mode">). When enabled
<productname>Pgpool-II</productname> sends the writing queries to the
- <acronym>primay node</acronym> in Master Slave mode, all of the
+ <acronym>primary node</acronym> in Master Slave mode, all of the
backend nodes in Replication mode, and other queries get load
balanced among all backend nodes. To which node the load
balancing mechanism sends read queries is decided at the session
@@ -145,7 +145,7 @@
/*REPLICATION*/ SELECT ...
</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.
</para>
@@ -493,7 +493,7 @@
<emphasis>DO NOT</emphasis> update the database. SELECTs including
functions <emphasis>not specified </emphasis> in this list are not load balanced.
These are replicated among all the DB nodes in Replication mode,
- sent to the primary node only in Maste Slave mode.
+ sent to the primary node only in Master Slave mode.
</para>
<para>
You can use regular expression to match function names,
@@ -516,7 +516,7 @@ white_function_list = 'get_.*,select_.*'
<para>
Schema qualifications can not be used
in <xref linkend="guc-white-function-list">
- because <productname>Pgpool-II</productname> slilently
+ because <productname>Pgpool-II</productname> silently
ignores a schema qualification in function names appearing
in an input SQL while comparing the list and the input
SQL. As a result, a schema qualified function name in the
@@ -544,7 +544,7 @@ white_function_list = 'get_.*,select_.*'
SELECTs including functions <emphasis>specified</emphasis> in this list are
not load balanced.
These are replicated among all the DB nodes in Replication mode,
- sent to the primary node only in Maste Slave mode.
+ sent to the primary node only in Master Slave mode.
</para>
<para>
You can use regular expression to match function names,
@@ -567,7 +567,7 @@ black_function_list = 'nextval,setval,set_.*,update_.*,delete_.*,insert_.*'
<para>
Schema qualifications can not be used
in <xref linkend="guc-black-function-list">
- because <productname>Pgpool-II</productname> slilently
+ because <productname>Pgpool-II</productname> silently
ignores a schema qualification in function names appearing
in an input SQL while comparing the list and the input
SQL. As a result, a schema qualified function name in the
@@ -627,7 +627,7 @@ black_function_list = 'nextval,setval,lastval,currval'
should be sent to primary node.
SQL that matched patterns specified in this list are
not load balanced.
- Only Maste Slave mode is supported.
+ Only Master Slave mode is supported.
</para>
<para>
You can use regular expression to match SQL patterns,
diff --git a/doc/src/sgml/misc-config.sgml b/doc/src/sgml/misc-config.sgml
index d094a1616..425bf5d4b 100644
--- a/doc/src/sgml/misc-config.sgml
+++ b/doc/src/sgml/misc-config.sgml
@@ -87,7 +87,7 @@
is used together.
</para>
<para>
- <productname>Pgpool-II</productname> searh relation cache on local
+ <productname>Pgpool-II</productname> search relation cache on local
for a cache entry first, if this is on. When it is not found on relation cache,
query cache is searched for it next. If it is found on query cache,
it is copied to relation cache on local. if a cache entry is not found
diff --git a/doc/src/sgml/online-recovery.sgml b/doc/src/sgml/online-recovery.sgml
index f0d542d9e..045a3e373 100644
--- a/doc/src/sgml/online-recovery.sgml
+++ b/doc/src/sgml/online-recovery.sgml
@@ -14,7 +14,7 @@
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.
</para>
<para>
@@ -64,8 +64,8 @@
<xref linkend="example-cluster-pgpool-config-online-recovery">.
</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 cliens are not allowed only in the second stage
+ while the data can be updated or retrieved during the first stage.
</para>
<para>
<productname>Pgpool-II</productname> performs the follows steps in online recovery:
@@ -226,7 +226,7 @@
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>.
</para>
<para>
@@ -273,7 +273,7 @@
<para>
<varname>recovery_1st_stage command</varname> runs as a <acronym>SQL</acronym>
command from PostgreSQL's point of view. So <varname>recovery_1st_stage command
- </varname> can get prematuraly killed by PostgreSQL if the PostgreSQL's
+ </varname> can get prematurely killed by PostgreSQL if the PostgreSQL's
<varname>statement_time_out</varname> is configured with the value that is
smaller than the time <varname>recovery_1st_stage_command</varname> takes for
completion.
@@ -359,7 +359,7 @@ rsync used in the command is killed by signal 2 for example.
<para>
<varname>recovery_2nd_stage command</varname> runs as a <acronym>SQL</acronym>
command from PostgreSQL's point of view. Therefore, <varname>recovery_2nd_stage command
- </varname> can get prematuraly killed by PostgreSQL if the PostgreSQL's
+ </varname> can get prematurely killed by PostgreSQL if the PostgreSQL's
<varname>statement_time_out</varname> is configured with the value that is
smaller than the time <varname>recovery_2nd_stage_command</varname> takes for
completion.
diff --git a/doc/src/sgml/performance.sgml b/doc/src/sgml/performance.sgml
index 19a964ee1..57fdc3fd1 100644
--- a/doc/src/sgml/performance.sgml
+++ b/doc/src/sgml/performance.sgml
@@ -270,13 +270,13 @@ Process memory requirement in total (in mega bytes) = <xref linkend="guc-num-ini
primary <productname>PostgreSQL</productname> which could be up
to as many as 10 queries. To reduce the
overhead, <productname>Pgpool-II</productname> maintains
- "relation cahche". Next time same table is included in a
+ "relation cache". Next time same table is included in a
query, <productname>Pgpool-II</productname> extracts the
- information from the cahe.
+ information from the cache.
</para>
<para>
There are some parameters to configure the relation
- cahce. See <xref linkend="guc-relcache-expire">, <xref linkend="guc-relcache-size">
+ cache. See <xref linkend="guc-relcache-expire">, <xref linkend="guc-relcache-size">
for more details.
</para>
@@ -290,7 +290,7 @@ Process memory requirement in total (in mega bytes) = <xref linkend="guc-num-ini
cache entry is created in all process, queries continue to
sent to <productname>PostgreSQL</productname>.
<productname>Pgpool-II</productname> 4.1 overcomes the issue
- by creating relation cachce in shared memory. If a session
+ by creating relation cache in shared memory. If a session
creates a relation cache entry in the shared memory, other
sessions will get the cache result by looking at the shared
relation
diff --git a/doc/src/sgml/release-4.0.sgml b/doc/src/sgml/release-4.0.sgml
index 4652f4eb7..d8f959d4c 100644
--- a/doc/src/sgml/release-4.0.sgml
+++ b/doc/src/sgml/release-4.0.sgml
@@ -70,7 +70,7 @@
(<ulink url="http://www.pgpool.net/mantisbt/view.php?id=487">bug 487</>) (Bo Peng)
</para>
<para>
- When all backend nodes are down, <productname>Pgpool-II</> throws an uncorrect
+ When all backend nodes are down, <productname>Pgpool-II</> throws an incorrect
error message "ERROR: connection cache is full". Change the error
message to "all backend nodes are down, pgpool requires at least one valid node".
</para>
@@ -513,7 +513,7 @@
</para>
<para>
If order of startup packet's parameters differ between cached connection
- pools and connection request, did't use connection pool ,and created new
+ pools and connection request, didn't use connection pool and created new
connection pool.
</para>
</listitem>
@@ -1004,7 +1004,7 @@ username3:TEXTmypassword
<para>
Specify a semicolon separated list of SQL patterns that
should be sent to primary node only. Regular expression can be
- used in SQL patterns. Only Maste Slave mode is supported.
+ used in SQL patterns. Only Master Slave mode is supported.
</para>
</listitem>
@@ -1218,7 +1218,7 @@ username3:TEXTmypassword
<para>
pgpool_setup -n 3 (or greater) triggers the bug. While recovering node
2, pgpool main process tried to retrieve version info from backend #2
- even if it's not running. This causes the sefault because connection
+ even if it's not running. This causes the segfault because connection
was not established yet. The reason why <productname>PostgreSQL 9.6</productname>
or later was not suffered from the bug was, <productname>PostgreSQL</productname>
exited the loop as soon as the server version is higher than 9.5. To fix this,
diff --git a/doc/src/sgml/restrictions.sgml b/doc/src/sgml/restrictions.sgml
index 62429ea4b..57a24dc25 100644
--- a/doc/src/sgml/restrictions.sgml
+++ b/doc/src/sgml/restrictions.sgml
@@ -4,7 +4,7 @@
<title>Restrictions</title>
<para>
- This section descibes current restrictions of <productname>Pgpool-II</productname>.
+ This section describes current restrictions of <productname>Pgpool-II</productname>.
<variablelist>
@@ -45,7 +45,7 @@
<para>
In the replication mode or master/slave 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
@@ -256,7 +256,7 @@ INSERT INTO rel1(c1) SELECT 1
<term>Multi-byte Characters</term>
<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.
</para>
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index c7cab3ce8..8f16e6547 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -211,7 +211,7 @@ password: <userinput>your_password</userinput>
responsible for synchronizing tables. Load balancing is possible
in the mode. Since logical replication does not replicate all
tables, it's user's responsibility to replicate the table which
- could be load balanced. <productname>Pgpool-II</> load balaces
+ could be load balanced. <productname>Pgpool-II</> load balances
all tables. This means that if a table is not
replicated, <productname>Pgpool-II</> may lookup outdated tables
in the subscriber side.
@@ -248,7 +248,7 @@ password: <userinput>your_password</userinput>
session Y commits data on node B. If session X tries to update
data on node B based on the data seen on node A, then data
consistency between node A and B might be lost. To avoid the
- problem, user need to issue an explict lock on the data. This is
+ problem, user need to issue an explicit lock on the data. This is
another reason why we recommend to use streaming replication
mode with <literal>synchronous_commit = remote_apply</literal>.
</para>
@@ -260,7 +260,7 @@ password: <userinput>your_password</userinput>
In the <firstterm>raw
mode</firstterm>, <productname>Pgpool-II</> does not care about
the database synchronization. It's user's responsibility to make
- the whole system does a meaningfull thing. Load balancing
+ the whole system does a meaningful thing. Load balancing
is <emphasis>not</emphasis> possible in the mode.
</para>
</sect2>
@@ -274,7 +274,7 @@ password: <userinput>your_password</userinput>
backend servers, you need to configure <varname>backend*</varname>
in <filename>pgpool.conf</filename>. For starters, at
least <xref linkend="guc-backend-hostname">
- and <xref linkend="guc-backend-port"> paramters are required to
+ and <xref linkend="guc-backend-port"> parameters are required to
be set up to start <productname>Pgpool-II</> server.
</para>
diff --git a/doc/src/sgml/watchdog.sgml b/doc/src/sgml/watchdog.sgml
index 815b4ddeb..7e3346567 100644
--- a/doc/src/sgml/watchdog.sgml
+++ b/doc/src/sgml/watchdog.sgml
@@ -87,7 +87,7 @@
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.
</para>
<para>
@@ -542,7 +542,7 @@
<literal>'query'</literal> or <literal>'external'</literal>.
</para>
<para>
- <literal>heartbeat</literal>: In this mode, watchdog sends the heartbeat singals (<acronym>UDP</acronym> packets)
+ <literal>heartbeat</literal>: In this mode, watchdog sends the heartbeat signals (<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
@@ -750,7 +750,7 @@
<para>
Specifies the <acronym>IP</acronym> address or <acronym>hostname</acronym> of destination the remote
<productname>Pgpool-II</productname> 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 "destination number", that starts from 0.
</para>
@@ -774,7 +774,7 @@
<para>
Specifies the destination port number of the remote
<productname>Pgpool-II</productname> 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 "destination number", that starts from 0.
</para>
[parent: 93a151708c7f]