Patch contributed by Umar Hayat.
Discussion: https://www.pgpool.net/pipermail/pgpool-hackers/2020-April/003587.html
the "NODES LIST DATA" result packet.
</para>
<para>
- The result packet returnd by watchdog for the "GET NODES LIST"
+ The result packet returned by watchdog for the "GET NODES LIST"
will contains the list of all configured watchdog nodes to do
health check on in the <acronym>JSON</acronym> format.
The <acronym>JSON</acronym> of the watchdog nodes contains the
status and brings the virtual IP assigned to watchdog down.
Thus clients of <productname>Pgpool-II</productname> cannot
connect to <productname>Pgpool-II</productname> using the
- virtual IP any more. This is neccessary to avoid split-brain,
+ virtual IP any more. This is necessary to avoid split-brain,
that is, situations where there are multiple active
<productname>Pgpool-II</productname>.
</para>
a <productname>PostgreSQL</productname> database client, so when a
client application connects to
the <productname>Pgpool-II</productname>, <productname>Pgpool-II</productname>
- inturn connects to the <productname>PostgreSQL</productname> servers
- using the same credentials to serve the incomming client
+ in
turn connects to the <productname>PostgreSQL</productname> 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</productname> gets
automatically applied to all <productname>Pgpool-II</productname>
<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.
</para>
<sect1 id="auth-pool-hba-conf">
</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
- <varname>serialize_accept</varname> or not, because the corelation
+ It is recommended to do a benchmark before deciding whether to use
+ <varname>serialize_accept</varname> or not, because the correlation
of <xref linkend="guc-num-init-children"> and <varname>serialize_accept</varname>
can be different on different environments.
</para>
</row>
<row>
- <entry>watchdog heart beat reciever</entry>
+ <entry>watchdog heart beat receiver</entry>
<entry>heart_beat_receiver</entry>
</row>
Clustering mode is the method to sync
<productname>PostgreSQL</productname> servers. To set the clustering
mode, <varname>backend_clustering_mode</varname> can be used. In
- this section we discusss how to set the clustering mode. See <xref
+ this section we discuss how to set the clustering mode. See <xref
linkend="planning-postgresql"> for more details.
</para>
</listitem>
<title>Streaming replication mode</title>
<para>
- This mode is most poplular and recommended clustering mode. In this
+ 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
<programlisting>
backend_clustering_mode = 'native_replication'
</programlisting>
- In this mode you can have up to 127 slabe replication servers.
+ In this mode you can have up to 127 slave replication servers.
Also it is possible not to have slave server at all.
</para>
<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.
+ doesn't have the SERIAL columns.
</para>
<para>
<xref linkend="guc-delegate-ip"> which we will not set in this example instead
we will use <xref linkend="guc-wd-escalation-command"> and
<xref linkend="guc-wd-de-escalation-command"> to switch the
- Elastic IP address to the maste/Active <productname>Pgpool-II</productname> node.
+ Elastic IP address to the maste
r/Active <productname>Pgpool-II</productname> node.
</para>
<sect3 id="example-AWS-pgpool-config-instance-1">
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.
</para>
</listitem>
Aurora writer node. Set
other <xref linkend="guc-backend-hostname"> for the
Aurora reader node. Set
- appropreate <xref linkend="guc-backend-weight"> as
+ appropriate <xref linkend="guc-backend-weight"> as
usual. You don't need to
set <xref linkend="guc-backend-data-directory">
</para>
$ cp /usr/local/etc/pgpool.conf.sample /usr/local/etc/pgpool.conf
</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>.
<programlisting>
listen_addresses = 'localhost'
<thead>
<row>
<entry>User Name</entry>
- <entry>Passowrd</entry>
+ <entry>Password</entry>
<entry>Detail</entry>
</row>
</thead>
To allow <literal>repl</literal> user without specifying password for streaming
replication and online recovery, and execute <application>pg_rewind</application>
using <literal>postgres</literal>, we create the <filename>.pgpass</filename> file
- in <literal>postgres</literal> user's home directory and change the permisson to
+ in <literal>postgres</literal> user's home directory and change the permission to
<literal>600</literal> on each <productname>PostgreSQL</productname> server.
</para>
<programlisting>
<para>
When installing <productname>Pgpool-II</productname> from RPM, all the
<productname>Pgpool-II</productname> configuration files are in <filename>/etc/pgpool-II</filename>.
- In this example, we copy the sample configuration file for streaming replicaton mode.
+ In this example, we copy the sample configuration file for streaming replication mode.
</para>
<programlisting>
# cp -p /etc/pgpool-II/pgpool.conf.sample-stream /etc/pgpool-II/pgpool.conf
health_check_max_retries = 3
</programlisting>
<para>
- Specify the <productname>PostgreSQL</productname> backend informations.
+ Specify the <productname>PostgreSQL</productname> backend information.
Multiple backends can be specified by adding a number at the end of the parameter name.
</para>
<programlisting>
</programlisting>
</para>
<para>
- Execute command <command>pg_enc -m -k /path/to/.pgpoolkey -u username -p</command> to regist user
+ Execute command <command>pg_enc -m -k /path/to/.pgpoolkey -u username -p</command> to register user
name and <literal>AES</literal> encrypted password in file <filename>pool_passwd</filename>.
If <filename>pool_passwd</filename> doesn't exist yet, it will be created in the same directory as
<filename>pgpool.conf</filename>.
</programlisting>
<para>
After executing <command>pcp_recovery_node</command> command,
- vertify that <literal>server2</literal> and <literal>server3</literal>
+ verify that <literal>server2</literal> and <literal>server3</literal>
are started as <productname>PostgreSQL</productname> standby server.
</para>
<programlisting>
</programlisting>
<para>
Start <productname>Pgpool-II</productname> (<literal>server1</literal>) which we have stopped again,
- and vertify that <literal>server1</literal> runs as a standby.
+ and verify that <literal>server1</literal> runs as a standby.
</para>
<programlisting>
[server1]# systemctl start pgpool.service
<title>Failover</title>
<para>
First, use <command>psql</command> to connect to <productname>PostgreSQL</productname> via virtual IP,
- and verify the backend informations.
+ and verify the backend information.
</para>
<programlisting>
# psql -h 192.168.137.150 -p 9999 -U pgpool postgres -c "show pool_nodes"
[root@osspc20]# {installed_dir}/bin/pgpool -n -f {installed_dir}/etc/pgpool.conf > pgpool.log 2>&1
</programlisting>
Log messages will show that <productname>Pgpool-II</productname>
- has joind the watchdog cluster as standby watchdog.
+ has joined the watchdog cluster as standby watchdog.
<programlisting>
LOG: watchdog cluster configured with 1 remote nodes
LOG: watchdog remote node:0 on Linux_osspc16_9000:9000
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.
</para>
<table id="ffailback-command-table">
<para>
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.
</para>
<para>
must be enabled, and <productname>PostgreSQL</productname> 9.1 or later
is required as backend nodes. This feature use <function>pg_stat_replicatoin</function>
on primary node, the automatic failback is performed to standby node only.
- Note that failback_command will be executed as well if failback_commnad is not empty.
+ Note that failback_command will be executed as well if failback_command is not empty.
If you plan to detach standby node for maintenance, set this parameter to off beforehand.
Otherwise it's possible that standby node is reattached against your intention.
</para>
<title>Installation from RPM</title>
<para>
This chapter describes the installation
- of <productname>Pgpool-II</productname> from PRM. If you are
+ of <productname>Pgpool-II</productname> from RPM. If you are
going to install from the source code, please
check <xref linkend="install-source">.
</para>
Although it is possible to use only one
<productname>Pgpool-II</productname>, we recommend to use more
than 1 <productname>Pgpool-II</productname> to avoid whole
- database inavailability due to the
+ database unavailability due to the
<productname>Pgpool-II</productname> being down. Multiple
<productname>Pgpool-II</productname> work together and monitor
each other. One of them is called "master" and it has a virtual
</para>
<para>
Since it is not allowed to have multiple master, watchdog votes to
- deicude a new master. If there are even number of
+ decide a new master. If there are even number of
<productname>Pgpool-II</productname>, it is impossible to decide
the new master by voting. Thus we recommend to deploy
<productname>Pgpool-II</productname> in more than 3 odd numbers.
<productname>PostgreSQL</productname> in streaming replication
mode in <xref linkend="example-cluster"> for those who want to
have a production level <productname>Pgpool-II</productname>
- installtion today.
+ installation today.
</para>
</sect2>
</sect1>
<para>
<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</productname> on the screen by use <function>pgpool_pgctl</function>.
- It is enough, if these function installed in template1 fisrt. These
+ It is enough, if these function installed in template1 first. These
function do not needed that install in all databases.
</para>
<listitem>
<para>
- COPY TO STODUT
+ COPY TO STDOUT
</para>
</listitem>
</para>
<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 master node (in other mode) depending on the
setting of <xref linkend="guc-disable-load-balance-on-write">.
</listitem>
<listitem>
<para>
- SQL including table_nama3
+ SQL including table_name3
</para>
</listitem>
</itemizedlist>
<caution>
<para>
- <acronym>JDBC</acronym> driver postgreSQL-9.3 and earlier versions
+ <acronym>JDBC</acronym> driver PostgreSQL-9.3 and earlier versions
does not send the application name in the startup packet even if
the application name is specified using the <acronym>JDBC</acronym>
driver option <literal>"ApplicationName"</literal> and
<literal>"assumeMinServerVersion=9.0"</literal>.
So if you want to use the <xref linkend="guc-app-name-redirect-preference-list">
- feature through <acronym>JDBC</acronym>, Use postgreSQL-9.4 or later version of the driver.
+ feature through <acronym>JDBC</acronym>, Use PostgreSQL-9.4 or later version of the driver.
</para>
</caution>
</para>
<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.
</para>
<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>
<varlistentry id="guc-relcache-query-target" xreflabel="relcache_query_target">
<term><varname>relcache_query_target</varname> (<type>enum</type>)
<indexterm>
- <primary><varname>relache_query_target</varname> configuration parameter</primary>
+ <primary><varname>relcache_query_target</varname> configuration parameter</primary>
</indexterm>
</term>
<listitem>
standby because it's much geographically closer. In this
case you can set backend_weight0 (this represents primary)
to 0, backend_weight1 to 1 (this represents standby) and set
- relache_query_target
+ relcache_query_target
to <literal>load_balance_node</literal>.
</para>
<para>
</para>
<note>
<para>
- For a backward compatibily sake for 4.0 or
+ For a backward compatibility sake for 4.0 or
before, <productname>Pgpool-II</productname>
accepts <literal>on</literal>, which is same
as <literal>catalog</literal> and <literal>off</literal>,
<xref linkend="example-cluster-pgpool-config-online-recovery">.
</para>
<para>
- Connections from cliens are not allowed only in the second stage
+ Connections from clients are not allowed only in the second stage
while the data can be updated or retrieved during the first stage.
</para>
<para>
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>
<para>
in <productname>Pgpool-II</productname>: shared memory and
process private memory. The former is allocated at the startup
of <productname>Pgpool-II</productname> main server process
- and will not be freeed until
+ and will not be freed until
whole <productname>Pgpool-II</productname> servers shut down.
The latter is allocated within
each <productname>Pgpool-II</productname> child process and
<title>Shared Memory Requirement</title>
<para>
- Here is a fomula to calculate the shared memory requirement.
+ Here is a formula to calculate the shared memory requirement.
<programlisting>
Shared memory requirement (in bytes) = <xref linkend="guc-num-init-children"> * <xref linkend="guc-max-pool"> * 17408
</programlisting>
<title>Process Memory Requirement</title>
<para>
- Here is a fomula to calculate the process memory requirement.
+ Here is a formula to calculate the process memory requirement.
<programlisting>
Process memory requirement in total (in mega bytes) = <xref linkend="guc-num-init-children"> * 5
</programlisting>
limit. There are several ways to deal with this problem.
</para>
- <sect2 id="controling-num-init-children">
- <title>Controling num_init_children</title>
+ <sect2 id="controlling-num-init-children">
+ <title>Controlling num_init_children</title>
<para>
The obvious way to deal with the problem is increasing the
number of child process. This can be done by
</para>
</sect2>
- <sect2 id="controling-listen-backlog-multiplier">
- <title>Controling listen_backlog_multiplier</title>
+ <sect2 id="controlling-listen-backlog-multiplier">
+ <title>Controlling listen_backlog_multiplier</title>
<para>
Another solution would be increasing the connection request
queue. This could be done by
the ratio specified by <xref linkend="guc-backend-weight">0
and
<xref linkend="guc-backend-weight">1. If those two values are
- eqaul, the chance each node is chosen will be even.
+ equal, the chance each node is chosen will be even.
</para>
<para>
or <xref linkend="guc-load-balance-mode"> is set to off,
sometimes <productname>Pgpool-II</productname> needs to
ask <productname>PostgreSQL</productname> to get meta
- information, such as whether a table is a temporay one or
+ information, such as whether a table is a temporary one or
not. To get those
- information, <productname>Pgpool-II</productname> sends queires
+ information, <productname>Pgpool-II</productname> sends queries
primary <productname>PostgreSQL</productname> which could be up
to as many as 10 queries (in 4.1 or after, the number of queries
has been decreased, it is not zero, however). To reduce the
<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>
<title>Description</title>
<para>
<command>pcp_detach_node</command>
- detaches the given node from Pgpool-II. Exisiting connections to Pgpool-II are forced to be disconnected.
+ detaches the given node from Pgpool-II. Existing connections to Pgpool-II are forced to be disconnected.
</para>
</refsect1>
Index 0 gets one's self watchdog information.
</para>
<para>
- If ommitted then gets information of all watchdog nodes.
+ If omitted then gets information of all watchdog nodes.
</para>
</listitem>
</varlistentry>
<listitem>
<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.
</para>
</listitem>
</varlistentry>
<para>
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.
</para>
</refsect1>
hostname, the port, the status, the weight (only meaningful if
you use the load balancing mode), the role, the SELECT query
counts issued to each backend, whether each node is the load
- bakance node or not, the replication delay (only if in streaming
+ balance node or not, the replication delay (only if in streaming
replication mode) and last status change time. In addition to
- this replicatin state and sync state are shown for standby nodes
+ this replication state and sync state are shown for standby nodes
in <productname>Pgpool-II</productname> 4.1 or after. The
possible values in the status column are explained in
the <xref linkend="pcp-node-info"> reference. If the hostname is
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).
</para>
<para>
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.
</para>
<sect1 id="installing-pgpool-adm">
</para>
<para>
- This status mismatch should be fixe by pcp_promote_node, but when the node
+ This status mismatch should be fixed by pcp_promote_node, but when the node
is the master node (the first alive node), it fails as mentioned above.
</para>
2016-12-28 [afebadf]
-->
<para>
- Fix authentication timeout that can occur right after client connecttions. (Yugo Nagata)
+ Fix authentication timeout that can occur right after client connections. (Yugo Nagata)
</para>
</listitem>
Change the <filename>pgpool.service</filename> and sysconfig files to output <productname>Pgpool-II</productname> log. (Bo Peng)
</para>
<para>
- Removeing "Type=forking" and add OPTS=" -n" to
+ Removing "Type=forking" and add OPTS=" -n" to
run <productname>Pgpool-II</productname> with non-daemon mode, because we need to redirect logs.
Using <command>"journalctl"</command> command to see <productname>Pgpool-II</productname> systemd log.
</para>
frontend. In most cases this is good. However if other than primary
node or master node returns an error state (this could happen if load
balance node is other than primary or master node and the query is an
- errornous SELECT), this should be returned to frontend, because the
+ erroneous SELECT), this should be returned to frontend, because the
frontend already received an error.
</para>
</listitem>
Fix bug mistakenly overriding global backend status right after failover. (Tatsuo Ishii)
</para>
<para>
- See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for mor details.
+ See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for more details.
</para>
</listitem>
2017-03-24 [dab2ff0]
-->
<para>
- Fix for 0000296: PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
+ Fix for 0000296: Pgpool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
<ulink url="http://www.pgpool.net/mantisbt/view.php?id=296">(Bug 296)</ulink> (Muhammad Usama)
</para>
</listitem>
</para>
<para>
- This status mismatch should be fixe by pcp_promote_node, but when the node
+ This status mismatch should be fixed by pcp_promote_node, but when the node
is the master node (the first alive node), it fails as mentioned above.
</para>
2016-12-28 [afebadf]
-->
<para>
- Fix authentication timeout that can occur right after client connecttions. (Yugo Nagata)
+ Fix authentication timeout that can occur right after client connections. (Yugo Nagata)
</para>
</listitem>
(<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>
</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>
</para>
<para>
In a explicit transaction, the <literal>SELECT</literal> results are cached in temporary buffer.
- If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffe should be reset.
+ If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffer should be reset.
</para>
</listitem>
Change the <filename>pgpool.service</filename> and sysconfig files to output <productname>Pgpool-II</productname> log. (Bo Peng)
</para>
<para>
- Removeing "Type=forking" and add OPTS=" -n" to
+ Removing "Type=forking" and add OPTS=" -n" to
run <productname>Pgpool-II</productname> with non-daemon mode, because we need to redirect logs.
Using <command>"journalctl"</command> command to see <productname>Pgpool-II</productname> systemd log.
</para>
frontend. In most cases this is good. However if other than primary
node or master node returns an error state (this could happen if load
balance node is other than primary or master node and the query is an
- errornous SELECT), this should be returned to frontend, because the
+ erroneous SELECT), this should be returned to frontend, because the
frontend already received an error.
</para>
</listitem>
Fix bug mistakenly overriding global backend status right after failover. (Tatsuo Ishii)
</para>
<para>
- See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for mor details.
+ See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for more details.
</para>
</listitem>
2017-03-24 [1172e6c]
-->
<para>
- Fix for 0000296: PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
+ Fix for 0000296: Pgpool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
<ulink url="http://www.pgpool.net/mantisbt/view.php?id=296">(Bug 296)</ulink> (Muhammad Usama)
</para>
</listitem>
</para>
<para>
- This status mismatch should be fixe by pcp_promote_node, but when the node
+ This status mismatch should be fixed by pcp_promote_node, but when the node
is the master node (the first alive node), it fails as mentioned above.
</para>
2016-12-28 [afebadf]
-->
<para>
- Fix authentication timeout that can occur right after client connecttions. (Yugo Nagata)
+ Fix authentication timeout that can occur right after client connections. (Yugo Nagata)
</para>
</listitem>
2020-01-28 [d60e6b7]
-->
<para>
- Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failire. (Bo Peng)
+ Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failure. (Bo Peng)
</para>
</listitem>
</itemizedlist>
2019-07-03 [380d8a5]
-->
<para>
- Fix sefault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
+ Fix se
gfault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
</para>
</listitem>
(<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>
</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>
</para>
<para>
In a explicit transaction, the <literal>SELECT</literal> results are cached in temporary buffer.
- If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffe should be reset.
+ If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffer should be reset.
</para>
</listitem>
Change the <filename>pgpool.service</filename> and sysconfig files to output <productname>Pgpool-II</productname> log. (Bo Peng)
</para>
<para>
- Removeing "Type=forking" and add OPTS=" -n" to
+ Removing "Type=forking" and add OPTS=" -n" to
run <productname>Pgpool-II</productname> with non-daemon mode, because we need to redirect logs.
Using <command>"journalctl"</command> command to see <productname>Pgpool-II</productname> systemd log.
</para>
frontend. In most cases this is good. However if other than primary
node or master node returns an error state (this could happen if load
balance node is other than primary or master node and the query is an
- errornous SELECT), this should be returned to frontend, because the
+ erroneous SELECT), this should be returned to frontend, because the
frontend already received an error.
</para>
</listitem>
Fix bug mistakenly overriding global backend status right after failover. (Tatsuo Ishii)
</para>
<para>
- See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for mor details.
+ See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for more details.
</para>
</listitem>
2017-09-01 [ad90886]
-->
<para>
- Fix <varname>wd_authkey</varname> bug in that a request to add new node to the clusetr is rejected by master. (Yugo Nagata)
+ Fix <varname>wd_authkey</varname> bug in that a request to add new node to the cluster is rejected by master. (Yugo Nagata)
</para>
<para>
This is a bug due to the implementation of 3.5.6 and 3.6.3.
2017-06-09 [b86e7b7]
-->
<para>
- Fix a posible hang with streaming replication and extended protocol (Yugo Nagata)
+ Fix a possible hang with streaming replication and extended protocol (Yugo Nagata)
</para>
<para>
- This hang occured under a certain condition. The following is an example.
+ This hang occurred under a certain condition. The following is an example.
</para>
<programlisting>
</programlisting>
<para>
- Without using <productname>JDBC</productname>, we can reproduce the problem by <productname>pgproto</productname> with the followeing messages.
+ Without using <productname>JDBC</productname>, we can reproduce the problem by <productname>pgproto</productname> with the following messages.
</para>
<programlisting>
2017-03-24 [d726c3a]
-->
<para>
- Fix for 0000296: PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
+ Fix for 0000296: Pgpool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
<ulink url="http://www.pgpool.net/mantisbt/view.php?id=296">(Bug 296)</ulink> (Muhammad Usama)
</para>
</listitem>
</para>
<para>
- This status mismatch should be fixe by pcp_promote_node, but when the node
+ This status mismatch should be fixed by pcp_promote_node, but when the node
is the master node (the first alive node), it fails as mentioned above.
</para>
2016-12-28 [afebadf]
-->
<para>
- Fix authentication timeout that can occur right after client connecttions. (Yugo Nagata)
+ Fix authentication timeout that can occur right after client connections. (Yugo Nagata)
</para>
</listitem>
</listitem>
<listitem>
<para>
- Pgool-II forward it to backend 1
+ Pgpool-II forward it to backend 1
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
- Pgool-II forward it to backend 0 & 1
+ Pgpool-II forward it to backend 0 & 1
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
- Pgool-II forward it to backend 0 & 1
+ Pgpool-II forward it to backend 0 & 1
</para>
</listitem>
<listitem>
2020-01-28 [d60e6b7]
-->
<para>
- Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failire. (Bo Peng)
+ Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failure. (Bo Peng)
</para>
</listitem>
</itemizedlist>
2019-09-04 [3ba4e73]
-->
<para>
- Doc: mention that VIP will not be brougt up if quorum does not exist. (Tatsuo Ishii)
+ Doc: mention that VIP will not be brought up if quorum does not exist. (Tatsuo Ishii)
</para>
<para>
2019-07-03 [380d8a5]
-->
<para>
- Fix sefault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
+ Fix se
gfault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
</para>
</listitem>
(<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>
</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>
</para>
<para>
In a explicit transaction, the <literal>SELECT</literal> results are cached in temporary buffer.
- If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffe should be reset.
+ If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffer should be reset.
</para>
</listitem>
Change the <filename>pgpool.service</filename> and sysconfig files to output <productname>Pgpool-II</productname> log. (Bo Peng)
</para>
<para>
- Removeing "Type=forking" and add OPTS=" -n" to
+ Removing "Type=forking" and add OPTS=" -n" to
run <productname>Pgpool-II</productname> with non-daemon mode, because we need to redirect logs.
Using <command>"journalctl"</command> command to see <productname>Pgpool-II</productname> systemd log.
</para>
frontend. In most cases this is good. However if other than primary
node or master node returns an error state (this could happen if load
balance node is other than primary or master node and the query is an
- errornous SELECT), this should be returned to frontend, because the
+ erroneous SELECT), this should be returned to frontend, because the
frontend already received an error.
</para>
</listitem>
Fix bug mistakenly overriding global backend status right after failover. (Tatsuo Ishii)
</para>
<para>
- See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for mor details.
+ See <ulink url="http://www.sraoss.jp/pipermail/pgpool-general/2017-September/005786.html">[pgpool-general: 5728]</ulink> for more details.
</para>
</listitem>
2017-09-01 [b661a8b]
-->
<para>
- Fix <varname>wd_authkey</varname> bug in that a request to add new node to the clusetr is rejected by master. (Yugo Nagata)
+ Fix <varname>wd_authkey</varname> bug in that a request to add new node to the cluster is rejected by master. (Yugo Nagata)
</para>
<para>
This is a bug due to the implementation of 3.5.6 and 3.6.3.
2017-08-21 [1812a84]
-->
<para>
- Doc: Add new English and Japanese documents of <link linkend="example-cluster">Pgpoo-II + Watchdog Setup Example</link>. (Bo Peng)
+ Doc: Add new English and Japanese documents of <link linkend="example-cluster">Pgpool-II + Watchdog Setup Example</link>. (Bo Peng)
</para>
</listitem>
2017-06-09 [d9b0b83]
-->
<para>
- Fix a posible hang with streaming replication and extended protocol. (Yugo Nagata)
+ Fix a possible hang with streaming replication and extended protocol. (Yugo Nagata)
</para>
<para>
- This hang occured under a certain condition. The following is an example.
+ This hang occurred under a certain condition. The following is an example.
</para>
<programlisting>
</programlisting>
<para>
- Without using <productname>JDBC</productname>, we can reproduce the problem by <productname>pgproto</productname> with the followeing messages.
+ Without using <productname>JDBC</productname>, we can reproduce the problem by <productname>pgproto</productname> with the following messages.
</para>
<programlisting>
2017-04-14 [50fb9a4]
-->
<para>
- Removing the function defined but not used warnings from pool_config_vatiable.c (Muhammad Usama)
+ Removing the function defined but not used warnings from pool_config_variable.c (Muhammad Usama)
</para>
</listitem>
2017-03-24 [c2a0cc5]
-->
<para>
- Fix for 0000296: PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
+ Fix for 0000296: Pgpool v3.6.2 terminated by systemd because the service Type has been set to 'forking'.
<ulink url="http://www.pgpool.net/mantisbt/view.php?id=296">(Bug 296)</ulink> (Muhammad Usama)
</para>
</listitem>
</para>
<para>
- This status mismatch should be fixe by pcp_promote_node, but when the node
+ This status mismatch should be fixed by pcp_promote_node, but when the node
is the master node (the first alive node), it fails as mentioned above.
</para>
2016-12-28 [afebadf]
-->
<para>
- Fix authentication timeout that can occur right after client connecttions. (Yugo Nagata)
+ Fix authentication timeout that can occur right after client connections. (Yugo Nagata)
</para>
</listitem>
</listitem>
<listitem>
<para>
- Pgool-II forward it to backend 1
+ Pgpool-II forward it to backend 1
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
- Pgool-II forward it to backend 0 & 1
+ Pgpool-II forward it to backend 0 & 1
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
- Pgool-II forward it to backend 0 & 1
+ Pgpool-II forward it to backend 0 & 1
</para>
</listitem>
<listitem>
restart. Watchdog not syncing status.
-->
<para>
- Sync inconsitent status
+ Sync inconsistent status
of <productname>PostgreSQL</productname> nodes
in <productname>Pgpool-II</productname> instances after
restart. (bug 218) (Muhammad Usama)
2016-08-18 [d3211dc] Let watchdog_setup to be installed.
-->
<para>
- Add new script called "watchdog_setup". (Tatstuo Ishii)
+ Add new script called "watchdog_setup". (Tatsuo Ishii)
</para>
<para>
<xref linkend="WATCHDOG-SETUP"> is a command to create a
Do not update status file if all backend nodes are in down status. (Chris Pacejo, Tatsuo Ishii)
</para>
<para>
- This commit tries to remove the data inconsitency in
+ This commit tries to remove the data inconsistency in
replication mode found
in <ulink url="http://www.pgpool.net/pipermail/pgpool-general/2015-August/003974.html">[pgpool-general:
3918]</ulink> by not recording the status file when all
-->
<para>
Change the default value of
- <xref linkend="guc-search-primary-node-timeout"> from 10 to 300. (Tatstuo Ishii)
+ <xref linkend="guc-search-primary-node-timeout"> from 10 to 300. (Tatsuo Ishii)
</para>
<para>
Prior default value 10 seconds is sometimes too short for a standby to
</listitem>
<listitem>
<!--
- 2016-08-01 [024eaea] Fix for 215: pgpool doesnt escalate ip in case of another node inavailability
+ 2016-08-01 [024eaea] Fix for 215: pgpool doesnt escalate ip in case of another node unavailability
-->
<para>
- Fix <productname>Pgpool-II</productname> doesn't escalate ip in case of another node inavailability. (bug 215) (Muhammad Usama)
+ Fix <productname>Pgpool-II</productname> doesn't escalate ip in case of another node unavailability. (bug 215) (Muhammad Usama)
</para>
<para>
The heartbeat receiver fails to identify the heartbeat sender watchdog node when
</listitem>
<listitem>
<!--
- 2016-06-08 [294cf4a] Fix a posible hang during health checking
+ 2016-06-08 [294cf4a] Fix a possible hang during health checking
-->
<para>
- Fix a posible hang during health checking. (bug 204) (Yugo Nagata)
+ Fix a possible hang during health checking. (bug 204) (Yugo Nagata)
</para>
<para>
- Helath checking was hang when any data wasn't sent
+ Health checking was hang when any data wasn't sent
from backend after <function>connect(2)</function> succeeded. To fix this,
<function>pool_check_fd()</function> returns 1 when <function>select(2)</function> exits with
- EINTR due to SIGALRM while health checkking is performed.
+ EINTR due to SIGALRM while health checking is performed.
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<!--
- 2016-05-11 [de905f6] Fix documetation bug about raw mode
+ 2016-05-11 [de905f6] Fix documentation bug about raw mode
-->
<para>
- Fix Japanese and Chinese documetation bug about raw mode. (Yugo Nagata, Bo Peng)
+ Fix Japanese and Chinese documentation bug about raw mode. (Yugo Nagata, Bo Peng)
</para>
<para>
- Connection pool is avalilable in raw mode.
+ Connection pool is available in raw mode.
</para>
</listitem>
<listitem>
Fix pgpool hung after receiving error state from backend. (bug #169) (Tatsuo Ishii)
</para>
<para>
- This could happend if we execute an extended protocol query and it
+ This could happen if we execute an extended protocol query and it
fails.
</para>
</listitem>
2016-03-03 [bb295a2] Fix query stack problems in extended protocol case.
-->
<para>
- Fix query stack problems in extended protocol case. (bug 167, 168) (Tatstuo Ishii)
+ Fix query stack problems in extended protocol case. (bug 167, 168) (Tatsuo Ishii)
</para>
<para>
</para>
</listitem>
<listitem>
<!--
- 2016-02-03 [48e9d4b] Fix for [pgpool-II 0000166]: compile issue on freebsd
+ 2016-02-03 [48e9d4b] Fix for [pgpool-II 0000166]: compile issue on FreeBSD
-->
<para>
- Fix compile issue on freebsd. (Muhammad Usama)
+ Fix compile issue on FreeBSD. (Muhammad Usama)
</para>
<para>
Add missing include files. The patch is contributed by
</para>
<para>
Sometimes <xref linkend="guc-wd-authkey"> calculation fails for some reason other than
- authkey mismatch. The additional messages make these distingushable
+ authkey mismatch. The additional messages make these distinguishable
for each other.
</para>
</listitem>
2020-01-28 [abbba81]
-->
<para>
- Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failire. (Bo Peng)
+ Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failure. (Bo Peng)
</para>
</listitem>
</itemizedlist>
2019-09-04 [3ba4e73]
-->
<para>
- Doc: mention that VIP will not be brougt up if quorum does not exist. (Tatsuo Ishii)
+ Doc: mention that VIP will not be brought up if quorum does not exist. (Tatsuo Ishii)
</para>
<para>
2019-07-03 [380d8a5]
-->
<para>
- Fix sefault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
+ Fix se
gfault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
</para>
</listitem>
(<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>
</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>
</para>
<para>
In a explicit transaction, the <literal>SELECT</literal> results are cached in temporary buffer.
- If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffe should be reset.
+ If a write <acronym>SQL</acronym> is sent which modifies the table, the temporary buffer should be reset.
</para>
</listitem>
Change the <filename>pgpool.service</filename> and sysconfig files to output <productname>Pgpool-II</productname> log. (Bo Peng)
</para>
<para>
- Removeing "Type=forking" and add OPTS=" -n" to
+ Removing "Type=forking" and add OPTS=" -n" to
run <productname>Pgpool-II</productname> with non-daemon mode, because we need to redirect logs.
Using <command>"journalctl"</command> command to see <productname>Pgpool-II</productname> systemd log.
</para>
frontend. In most cases this is good. However if other than primary
node or master node returns an error state (this could happen if load
balance node is other than primary or master node and the query is an
- errornous SELECT), this should be returned to frontend, because the
+ erroneous SELECT), this should be returned to frontend, because the
frontend already received an error.
</para>
</listitem>
2017-09-19 [34922b5]
-->
<para>
- Test: Add new test 011.watchdoc_quorum_failover. (Tatsuo Ishii)
+ Test: Add new test 011.watchdog_quorum_failover. (Tatsuo Ishii)
</para>
</listitem>
2020-01-28 [304e091]
-->
<para>
- Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failire. (Bo Peng)
+ Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failure. (Bo Peng)
</para>
</listitem>
</itemizedlist>
2020-01-28 [f8bbd91]
-->
<para>
- Doc: Change the sample follow_master_command script %M %H paramater's order. (Bo Peng)
+ Doc: Change the sample follow_master_command script %M %H parameter's order. (Bo Peng)
</para>
<para>
2019-09-04 [3ba4e73]
-->
<para>
- Doc: mention that VIP will not be brougt up if quorum does not exist. (Tatsuo Ishii)
+ Doc: mention that VIP will not be brought up if quorum does not exist. (Tatsuo Ishii)
</para>
<para>
2019-07-03 [5d042e4]
-->
<para>
- Fix sefault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
+ Fix se
gfault when query cache is enabled. (<ulink url="https://www.pgpool.net/mantisbt/view.php?id=525">bug 525</ulink>) (Tatsuo Ishii)
</para>
</listitem>
<sect2>
<title>Overview</title>
<para>
- This version addes support for SCRAM and CERT authentication,
+ This version adds support for SCRAM and CERT authentication,
improves load balancing control and import PostgreSQL 11
new SQL parser.
</para>
2020-01-28 [b0b52ef]
-->
<para>
- Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failire. (Bo Peng)
+ Check if socket file exists at startup and remove them if PID file doesn't exist to avoid bind() failure. (Bo Peng)
</para>
</listitem>
</itemizedlist>
2020-01-10 [d0252d8]
-->
<para>
- Doc: Change the sample follow_master_command script %M %H paramater's order. (Bo Peng)
+ Doc: Change the sample follow_master_command script %M %H parameter's order. (Bo Peng)
</para>
</listitem>
<para>
Add parameter <xref
linkend="guc-enable-consensus-with-half-votes"> to configure
- majority rule calculations. (Muhammd Usama, Tatsuo Ishii)
+ majority rule calculations. (Muhammad Usama, Tatsuo Ishii)
</para>
<para>
This changes the behavior of the decision of quorum existence and
affected. When this parameter is off (the default), a 2 node
watchdog cluster needs to have both 2 nodes are alive to have a
quorum. If the quorum does not exist and 1 node goes down, then
- 1) VIP will be lost, 2) failover srcript is not executed and 3)
+ 1) VIP will be lost, 2) failover script is not executed and 3)
no watchdog master exists. Especially #2 could be troublesome
because no new primary <productname>PostgreSQL</productname>
exists if existing primary goes down. Probably 2 node watchdog
-->
<para>
Performance enhancements for the large INSERT and UPDATE
- statements. (Muhammd Usama)
+ statements. (Muhammad Usama)
</para>
<para>
<productname>Pgpool-II</productname> only needs very little
Import PostgreSQL 12 beta2 new parser. (Bo Peng)
</para>
<para>
- Major chanegs of PostgreSQL 12 parser include:
+ Major changes of PostgreSQL 12 parser include:
<itemizedlist>
<listitem>
we set <xref linkend="guc-disable-load-balance-on-write"> =
<literal>transaction</literal>, when a write query is issued
inside an explicit truncation, subsequent queries should be
- sent to primary only until the end of this transactionin in
+ sent to primary only until the end of this transaction in
order to avoid the replication delay. However, the SELECTs
having write functions specified
in <xref linkend="guc-black-function-list"> or not specified
-->
<para>
Resign the master watchdog node from master responsibilities if
- the primary backend node gets into quarantine state on that. (Muhammd Usama)
+ the primary backend node gets into quarantine state on that. (Muhammad Usama)
</para>
<para>
By doing this, we could avoid the situation on which there's no
<para>
Add parameter <xref
linkend="guc-enable-consensus-with-half-votes"> to configure
- majority rule calculations. (Muhammd Usama, Tatsuo Ishii)
+ majority rule calculations. (Muhammad Usama, Tatsuo Ishii)
</para>
<para>
<productname>Pgpool-II</productname> takes the decision of quorum
<listitem>
<para>
Mention that schema qualifications cannot be used in
- Add performance chapterwhite/black_function_list. (tatsuo
- Ishii)
+ white/black_function_list. (tatsuo Ishii)
</para>
</listitem>
<!-- doc/src/sgml/config.sgml -->
<sect1 id="runtime-ssl">
- <title>Secure Sockect Layer (SSL)</title>
+ <title>Secure Socket Layer (SSL)</title>
<sect2 id="runtime-config-ssl-settings">
<listitem>
<para>
Specifies the name of the file containing Diffie-Hellman parameters
- used for so-called ephemeral DH family of SSl ciphers. The default is
+ used for so-called ephemeral DH family of SSL ciphers. The default is
empty. In which case compiled-in default DH parameters used. Using
Custom DH parameters reduces the exposure if an attacker manages to
crack the well-known compiled-in DH parameters. You can create your own
<para>
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.
</para>
<para>
</para>
<para>
<figure>
- <title>Process architecure of <productname>Pgpool-II</productname></title>
+ <title>Process architec
ture of <productname>Pgpool-II</productname></title>
<mediaobject>
<imageobject>
<imagedata fileref="process-diagram.gif">
</para>
<para>
- This parameter can be changed by reloading the <productname>Pgpool-II conf</>igurations.
+ This parameter can be changed by reloading the <productname>Pgpool-II</>configurations.
</para>
</listitem>
</sect2>
<sect2 id="config-watchdog-escalation-de-escalation">
- <title>Behaivor on escalation and de-escalation</title>
+ <title>Behaviour on escalation and de-escalation</title>
<para>
Configuration about behavior when <productname>Pgpool-II</productname>
<listitem>
<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 inconsistent to the old active.
</para>
<para>
Default is on.
solved.
</para>
<para>
- From <productname>Pgpool-II </productname><emphasis>V4.1</emphasis> onwards, if the watchdog-master node
+ From <productname>Pgpool-II </productname><emphasis>V4.1</emphasis> onward, if the watchdog-master node
fails to build the consensus for primary backend node failover and the primary backend node gets into a
quarantine state, then it resigns from its master/coordinator responsibilities and lowers its wd_priority
for next leader election and let the cluster elect some different new leader.
projects / pgpool2.git / commitdiff