pgpool2.git / summary / log / commit / refs
commit b712604665827c0644f9ccd26812aa76c5d7ddef
Author: Tatsuo Ishii <ishii@postgresql.org>
Date: Sat May 11 09:13:24 2013 +0000
Fixes from Bruce Momjian.
doc/pgpool-en.html | 62 ++++++++++++++--------------
doc/tutorial-en.html | 111 ++++++++++++++++++++++++++-------------------------
2 files changed, 87 insertions(+), 86 deletions(-)
diff --git a/doc/pgpool-en.html b/doc/pgpool-en.html
index 80b293146..cd874da15 100644
--- a/doc/pgpool-en.html
+++ b/doc/pgpool-en.html
@@ -7,7 +7,7 @@
</head>
<!-- hhmts start -->
-Last modified: Fri Mar 15 18:02:22 JST 2013
+Last modified: Sat May 11 17:47:15 JST 2013
<!-- hhmts end -->
<body bgcolor="#ffffff">
@@ -374,7 +374,7 @@ can collect pgpool-II status, and terminate pgpool-II processes remotely.
authentication by this interface. All operation modes require the
<code>pcp.conf</code> file to be set. A <code>$prefix/etc/pcp.conf.sample</code>
file is created during the installation of pgpool-II. Rename the file to
-<code>pcp.conf</code> and add your username and password to it.
+<code>pcp.conf</code> and add your user name and password to it.
</p>
<pre>
@@ -382,7 +382,7 @@ cp $prefix/etc/pcp.conf.sample $prefix/etc/pcp.conf
</pre>
<p>
An empty line or a line starting with "<code>#</code>" is treated as a
-comment and will be ignored. A username and its associated password must be
+comment and will be ignored. A user name and its associated password must be
written as one line using the following format:
</p>
<pre>
@@ -1209,7 +1209,7 @@ Following parameters take effect to connection pool.</p>
<dd>
<p>The maximum number of cached connections in pgpool-II children processes.
pgpool-II reuses the cached connection if an incoming connection is
- connecting to the same database with the same username.
+ connecting to the same database with the same user name.
If not, pgpool-II creates a new connection to the backend.
If the number of cached connections exceeds max_pool,
the oldest connection will be discarded, and uses that slot for the new connection.
@@ -1477,7 +1477,7 @@ COMMIT;
(more precisely, access error on pg_clog, which keeps transaction status).
To prevent this, PostgreSQL core developers decided to disallow row locking
against sequences and this will break pgpool-II of course
- (the "fixed" version of PostgreSQL will be released as 9.0.5,
+ (the "fixed" version of PostgreSQL was released as 9.0.5,
8.4.9, 8.3.16 and 8.2.22).
</p>
<p>
@@ -1526,7 +1526,7 @@ end of transaction block
<dt><a name="RECOVERY_USER"></a>recovery_user</dt>
<dd>
<p>
- This parameter specifies a PostgreSQL username for online recovery.
+ This parameter specifies a PostgreSQL user name for online recovery.
It can be changed without restarting.
</p>
</dd>
@@ -2258,7 +2258,7 @@ pgpool-II. The System DB's configuration is done in
<dt><a name="SYSTEM_DB_USER"></a>system_db_user</dt>
<dd>
- <p>The username to connect to the System DB.</p>
+ <p>The user name to connect to the System DB.</p>
</dd>
<dt><a name="SYSTEM_DB_PASSWORD"></a>system_db_password</dt>
@@ -2429,7 +2429,7 @@ Here are the limitations of pool_hba.
<ul>
<li>"hostssl" connection type is not supported</li>
<p>
- Though "hostssl" is invalid, pgpool-II 2.3 or later supports SSL.
+ Even if the SSL support is enabled, "hostssl" cannot be used.
See <a href="#ssl">SSL</a> for more details.
</p>
@@ -3650,9 +3650,9 @@ The procedure to update primary PostgreSQL server is as follows:
<h1><a name="backup"></a>Backup</h1>
<p>
-To back up backend PostgreSQL servers and system DB, you can physical
+To back up backend PostgreSQL servers and system DB, you can use physical
backup, logical backup (pg_dump, pg_dumpall) and PITR in the same manner as PostgreSQL.
-Please note that using logical backup and PITR should be performed directory PostgreSQL,
+Please note that using logical backup and PITR should be performed directory with PostgreSQL,
rather than via pgpool-II to avoid errors caused by <a href="#LOAD_BALANCE_MODE">load_balance_mode</a> and
<a href="#REPLICATE_SELECT">replicate_select</a>.
</p>
@@ -3721,9 +3721,9 @@ to make those deployments and pros and cons.
<p>
Pgpool-II is running on a dedicated server.
It's simple and pgpool-II is not affected by other server softwares.
- Obvious cons is you need to by more hardware.
+ Obvious cons is you need to buy more hardware.
Also pgpool-II can be a single point of failure with this configuration
- (you can avoid this by using pgpool-HA described somewhere below).
+ (you can avoid this by using pgpool-HA described described below).
</p>
</dd>
@@ -3733,7 +3733,7 @@ to make those deployments and pros and cons.
Deploying pgpool-II on a server where Apache, JBoss, Tomcat or other web
server and application servers.
Since communication between pgpool-II and web servers and application servers
- is within a local machine, socket communication can be faster than inter sever communication.
+ is within a local machine, socket communication can be faster than inter-sever communication.
Also if you are using multiple web serves or application servers, you can avoid
the single point of failure problem
(in this case you must have identical pgpool.conf on each pgpool-II instance).
@@ -3760,7 +3760,7 @@ to make those deployments and pros and cons.
Running pgpool-II on the server as PostgreSQL is running on.
You can avoid the single point of failure problem of pgpool-II with configuration.
And obviously you do need to buy additional dedicated server.
- Problem with this configuration is, application need to aware that which DB server they should connect to.
+ Problem with this configuration is, application need to aware of which DB server they should connect to.
To solve the problem you can use virtual IP with pgpool-HA.
</p>
</dd>
@@ -3768,9 +3768,9 @@ to make those deployments and pros and cons.
<h2 id="pgpool_ha">About pgpool-HA</h2>
<p>
-Pgpool-HA is a high availability software for pgpool-II using hearbeat.
-Pgpool-HA is a sub project of pgpool project as well as pgpool-II.
-Pgpool-HA can be available from pgpool development site as an open source software.
+Pgpool-HA is a high availability software for pgpool-II using heartbeat.
+Pgpool-HA is a sub-project of the pgpool project as well as pgpool-II.
+Pgpool-HA can be available from the pgpool development site as an open source software.
</p>
<p class="top_link"><a href="#Top">back to top</a></p>
@@ -3780,7 +3780,7 @@ Pgpool-HA can be available from pgpool development site as an open source softwa
<h1 id="watchdog">Watchdog <span class="version">V3.2 -</span></h1>
<p>
-"Watchdog" is a sub process of pgpool-II aiming for adding high availability feature to it.
+"Watchdog" is a sub process of pgpool-II to add high availability.
Features added by watchdog include:
</p>
@@ -3793,9 +3793,9 @@ Features added by watchdog include:
by watchdog and watchdog checks the response.
</p>
<p>
- Also watchdog monitors connections to up stream servers
+ Also watchdog monitors connections to upstream servers
(application servers etc.) from the pgpool.
- The connection between the up stream servers and the pgpool is monitored as service of pgpool.
+ The connection between the upstream servers and the pgpool is monitored as a service of pgpool.
</p>
</dd>
@@ -3812,7 +3812,7 @@ Features added by watchdog include:
<dd>
<p>
When a fault is detected in the pgpool service, watchdog notifies the other watchdogs of it.
- Watchdogs decide the new active pgpool if previous active pgpool is broken
+ Watchdogs then decide the new active pgpool if previous active pgpool is broken
by voting and change active/standby state.
</p>
</dd>
@@ -3822,7 +3822,7 @@ Features added by watchdog include:
<p>
When a standby pgpool server promotes to active, the new active server brings up virtual IP interface.
Meanwhile, the previous active server brings down the virtual IP interface.
- This enables the active pgpool to work using the same IP address even when servers is switched over.
+ This enables the active pgpool to work using the same IP address even when servers are switched.
</p>
</dd>
@@ -3832,7 +3832,7 @@ Features added by watchdog include:
When broken server recovers or new server is attached,
the watchdog process notifies the other watchdog process along with information of the new server,
and the watchdog process receives information on the active server and other servers.
- Then, the attached server is registered as standby.
+ Then, the attached server is registered as a standby.
</p>
</dd>
</dl>
@@ -3857,7 +3857,7 @@ The life checking starts after waiting for all of the pgpools to start.
<h2>Configuring watchdog (pgpool.conf)</h2>
<p>
-Watchdog configuration parameters is described in pgpool.conf.
+Watchdog configuration parameters are described in pgpool.conf.
There is sample configuration in WATCHDOG section in pgpool.conf.sample file.
</p>
<p>
@@ -4509,7 +4509,7 @@ be performed inside the functions.</p>
<h3>Extended Query Protocol (for parallel mode)</h3>
<p>The extended query protocol used by JDBC drivers, etc. is not
-supported. The simple query protocol must be used. This means you can't use
+supported. The simple query protocol must be used. This means you cannot use
prepared statements.</p>
<h3 id="ng_natural_join">Natural Join (for parallel mode)</h3>
@@ -4632,7 +4632,7 @@ fail. Also, the System DB must be PostgreSQL 7.4 or later.</p>
<h2 id="caution_query_cache">Query Cache</h2>
<p>With <a href="#query_cache">on disk query cache, invalidation must be done manually.
-This does not apply to <a href="#memqcache">on memory query cache</a>. Cacche invalidation is automatically done with on memory query cache.</p>
+This does not apply to <a href="#memqcache">on memory query cache</a>. Cache invalidation is automatically done with on memory query cache.</p>
<h2>Compatibility with pgpool</h2>
@@ -4684,11 +4684,11 @@ First argument - timeout value in seconds. PCP disconnects if
pgpool-II does not respond in this many seconds.
Second argument - pgpool-II's hostname
Third argument - PCP port number
-Fourth argument - PCP username
+Fourth argument - PCP user name
Fifth argument - PCP password
</pre>
-<p>PCP usernames and passwords must be declared in
+<p>PCP user names and passwords must be declared in
<code>pcp.conf</code> in <code>$prefix/etc</code>
directory. <code>-F</code> option can be used when starting pgpool-II
if <code>pcp.conf</code> is placed somewhere else. The password does
@@ -4787,7 +4787,7 @@ postgres_db postgres 1150769932 1150767351 3 0 1 1468 1
The result is in the following order:
1. connected database name
-2. connected username
+2. connected user name
3. process start-up timestamp
4. connection created timestamp
5. protocol major version
@@ -4879,7 +4879,7 @@ First, the System DB information will be displayed on the first
line. The result is in the following order:
1. hostname
2. port number
-3. username
+3. user name
4. password. '' for no password.
5. schema name
6. database name
@@ -5012,7 +5012,7 @@ error had occurred, it will exit with the following error status.
<!-- ================================================================================ -->
-<h1>Inside information<a name="internal"></a></h1>
+<h1>Internal information<a name="internal"></a></h1>
<p>
pgpool-II version 2.0.x brings extensive modifications, compared with the version 1.x
Please note that what follows doesn't apply to version 1.x.
diff --git a/doc/tutorial-en.html b/doc/tutorial-en.html
index 815d3d217..c446cc922 100644
--- a/doc/tutorial-en.html
+++ b/doc/tutorial-en.html
@@ -13,7 +13,7 @@
<p>Welcome to the Tutorial for pgpool-II. From here, you can learn how
to install, setup, and run parallel queries or do replication using
pgpool-II. We assume that you already know basic PostreSQL operations,
-so please refer to the PostgreSQL document if needed.</p>
+so please refer to the PostgreSQL document if neccesary.</p>
<dl>
<dt><em>Table of Contents</em></dt>
@@ -37,7 +37,7 @@ so please refer to the PostgreSQL document if needed.</p>
<h2>1. <a name="start">Let's Begin!</a></h2>
-<p>First, we must learn how to install, configure pgpool-II and
+<p>First, we must learn how to install and configure pgpool-II and
database nodes before using replication or parallel query.</p>
<h3>1.1. <a name="install">Installing pgpool-II</a></h3>
@@ -65,19 +65,19 @@ permission on the installation directory.</p>
<code>/usr/local</code> directory.</p>
<p><em>Note</em>: pgpool-II requires libpq library in PostgreSQL 7.4
-or later (version 3 protocol). If <code>configure</code> script
-displays the following error message, libpq library may not be
+or later (version 3 protocol). If the <code>configure</code> script
+displays the following error message, the libpq library may not be
installed, or it is not of version 3.</p>
<pre>configure: error: libpq is not installed or libpq is old</pre>
-<p>If the library is version 3, but above message is still displayed,
+<p>If the library is version 3, but the above message is still displayed,
your libpq library is probably not recognized by
-<code>configure</code> script.</p>
+the <code>configure</code> script.</p>
-<p><code>configure</code> script searches for libpq library under
-<code>/usr/local/pgsql</code> libaray. If you have installed
-PostgreSQL to a directory other than <code>/usr/local/pgsql</code>,
+<p>The <code>configure</code> script searches for libpq library under
+<code>/usr/local/pgsql</code>. If you have installed
+PostgreSQL in a directory other than <code>/usr/local/pgsql</code>,
use <code>--with-pgsql</code>, or <code>--with-pgsql-includedir</code>
and <code>--with-pgsql-libdir</code> command line options when you
execute <code>configure</code>.</p>
@@ -85,7 +85,7 @@ execute <code>configure</code>.</p>
<h3>1.2. <a name="config">Configuration Files</a></h3>
<p>pgpool-II configuration parameters are saved in
-<code>pgpool.conf</code> file. The file is in "<code>parameter =
+the <code>pgpool.conf</code> file. The file is in "<code>parameter =
value</code>" per line format. When you install pgpool-II,
<code>pgpool.conf.sample</code> is automatically created. We recommend
copying and renaming it to <code>pgpool.conf</code>, and edit it as
@@ -106,12 +106,12 @@ port = 9999
<h3>1.3. <a name="pcp-config">Configuring PCP Commands</a></h3>
-<p>pgpool-II has an interface for administration purpose to retrieve
+<p>pgpool-II has an interface for administrative purpose to retrieve
information on database nodes, shutdown pgpool-II, etc. via
network. To use PCP commands, user authentication is required. This
authentication is different from PostgreSQL's user authentication. A
-username and password need to be defined in <code>pcp.conf</code>
-file. In the file, a username and password are listed as a pair on
+user name and password need to be defined in the <code>pcp.conf</code>
+file. In the file, a user name and password are listed as a pair on
each line, and they are separated by a colon (:). Passwords are
encrypted in md5 hash format.</p>
@@ -123,13 +123,13 @@ automatically created. We recommend copying and renaming it to
</p>
<pre>$ cp /usr/local/etc/pcp.conf.sample /usr/local/etc/pcp.conf</pre>
-<p>To encrypt your password into md5 hash format, use pg_md5 command,
-which is installed as a part of pgpool-II
-executables. <code>pg_md5</code> takes text as an command line
+<p>To encrypt your password into md5 hash format, use the pg_md5 command,
+which is installed as one of pgpool-II's
+executables. <code>pg_md5</code> takes text as a command line
argument, and displays its md5-hashed text.</p>
-<p>For example, give "postgres" as the command line argument, at
-<code>pg_md5</code> displays md5-hashed text to the standard
+<p>For example, give "postgres" as the command line argument, and
+<code>pg_md5</code> displays md5-hashed text on its standard
output.</p>
<pre>
@@ -189,7 +189,7 @@ SELECT queries are equally distributed among three servers.</p>
<p>The above command, however, prints no log messages because pgpool
detaches the terminal. If you want to show pgpool log messages, you
-pass <code>-n</code> option to pgpool command. pgpool-II is executed
+pass <code>-n</code> option to pgpool command so pgpool-II is executed
as non-daemon process, and the terminal will not be detached.
</p>
@@ -199,37 +199,37 @@ $ pgpool -n &
<p>
The log messages are printed on the terminal, so the recommended
-options to use are like the following.
+options to use the following.
</p>
<pre>$ pgpool -n -d > /tmp/pgpool.log 2>&1 &</pre>
-<p><code>-d</code> option enables debug messages to be generated.</p>
+<p>The <code>-d</code> option enables debug messages to be generated.</p>
<p>
The above command keeps appending log messages to /tmp/pgpool.log. If
you need to rotate log files, pass the logs to a external command
-which have log rotation function.
+which has log rotation function.
-For example, you can use rotatelogs coming with Apache2:
+For example, you can use rotatelogs from Apache2:
<pre>
$ pgpool -n 2>&1 | /usr/local/apache2/bin/rotatelogs \
-l -f /var/log/pgpool/pgpool.log.%A 86400 &
</pre>
-This will generate a log file named "pgpool.log.Thursday" everyday then
-rotate it 00:00 at midnight. Rotatelogs adds log to a file if it already
+This will generate a log file named "pgpool.log.Thursday" then
+rotate it 00:00 at midnight. Rotatelogs adds logs to a file if it already
exists. To delete old log files before rotation, you could use cron:
<pre>
55 23 * * * /usr/bin/find /var/log/pgpool -type f -mtime +5 -exec /bin/rm -f '{}' \;
</pre>
-Please note that rotaelogs may exist as /usr/sbin/rotatelogs2 in some
+Please note that rotatelogs may exist as /usr/sbin/rotatelogs2 in some
distributions.
-f option generates a log file as soon as rotatelogs starts and is
-available apache2 2.2.9 or greater.
+available in apache2 2.2.9 or greater.
</p>
<p>
Also <a
-href="http://www.cronolog.org"><code>cronolog</code></a> helps you.
+href="http://www.cronolog.org"><code>cronolog</code></a> can be used.
</p>
<pre>
@@ -238,12 +238,12 @@ $ pgpool -n 2>&1 | /usr/sbin/cronolog \
'/var/log/pgsql/%Y-%m-%d-pgpool.log' &
</pre>
-<p>To stop pgpool-II process, execute the following command.</p>
+<p>To stop pgpool-II, execute the following command.</p>
<pre>$ pgpool stop</pre>
-<p>If any client is still connected, pgpool-II waits for them to
-disconnect, and then terminate itself. Execute the following command
+<p>If any client is still connected, pgpool-II waits for it to
+disconnect, and then terminates itself. Run the following command
instead if you want to shutdown pgpool-II forcibly.
<pre>$ pgpool -m fast stop</pre>
@@ -256,7 +256,7 @@ nodes.</p>
<p>In this section, we'll use three database nodes, which we have
already set up in section "1. <a href="#start">Let's Begin!</a>", and
takes you step by step to create a database replication system. Sample
-data to be replicated will be generated by pgbench benchmark
+data to be replicated will be generated by the pgbench benchmark
program.</p>
<h3>2.1. <a name="replication-config">Configuring Replication</a></h3>
@@ -286,11 +286,11 @@ href="#start-shutdown">Starting/Stopping pgpool-II</a>".</p>
<p>After configuring <code>pgpool.conf</code> and restarting
pgpool-II, let's try the actual replication and see if everything is
-working OK.</p>
+working.</p>
<p>First, we need to create a database to be replicated. We will name
it "bench_replication". This database needs to be created on all the
-nodes. Use <code>createdb</code> commands through pgpool-II, and the
+nodes. Use the <code>createdb</code> commands through pgpool-II, and the
database will be created on all the nodes.</p>
<pre>$ createdb -p 9999 bench_replication</pre>
@@ -344,9 +344,9 @@ branches, tellers, accounts, and history tables on all the nodes (5432,
<h2>3. <a name="parallel">Your First Parallel Query</a></h2>
<p>
-Data within the different range is stored in two or more data base nodes in a parallel Query. This is called a partitioning.
+Data within the range is stored in two or more data base nodes in a parallel Query. This is called a partitioning.
Moreover you could replicate some of tables among database nodes even
-in the parallel query mode.
+in parallel query mode.
</p>
<p>To enable parallel query in pgpool-II, you must set up another
@@ -382,10 +382,11 @@ configured so that pgpool-II accepts those connections.</p>
Attention: The replication is not done for the table that does the partitioning
though a parallel Query and the replication can be made effective at the same time.
+<p>
Attention: You can have both partitioned tables and replicated
-tables. However a table cannot be a partioned and replicated one at
+tables. However a table cannot be a partioned and replicated at
the same time. Because the data structure of partioned tables and
-replicated tables are different, "bench_replication" database created
+replicated tables is different, "bench_replication" database created
in section "2. <a href="#replication">Your First Replication</a>"
cannot be reused in parallel query mode.</p>
@@ -407,13 +408,13 @@ load_balance_mode = true
<h3>3.2. <a name="system-db">Configuring SystemDB</a></h3>
<p> "System database" is just an ordinaly database. The only
-requirement is, dblink functions and the dist_def table, which
+requirement is that dblink functions and the dist_def table, which
describes partioning rule, must be installed in the system
-database. You could have system database on a database node, or you
-could have multiple node having system database by using cascade
-configuration of pgpool-II. </p>
+database. You could have a system database on a database node, or you
+could have multiple nodes having system database by using cascade
+configuration in pgpool-II. </p>
-<p>In this section, we will create SystemDB within the 5432 port
+<p>In this section, we will create SystemDB on the 5432 port
node. The following list is the configuration parameters for
SystemDB</p>
@@ -438,7 +439,7 @@ $ createdb -p 5432 -O pgpool pgpool
<h4><p>3.2.1. Installing dblink</p></h4>
<p>Next, we must install dblink into "pgpool" database. dblink is one
-of the tools included in <code>contrib</code> directory in the
+of the tools included in the <code>contrib</code> directory in the
PostgreSQL source code.</p>
<p>To install dblink to your system, execute the following commands.</p>
@@ -449,7 +450,7 @@ $ USE_PGXS=1 make -C contrib/dblink install
</pre>
<p>After dblink has been installed into your system, we will define
-dblink functions in "pgpool" database. If PostgreSQL is installed in
+dblink functions in the "pgpool" database. If PostgreSQL is installed in
<code>/usr/local/pgsql</code>, <code>dblink.sql</code> (a file with
function definitions) should have been installed in
<code>/usr/local/pgsql/share/contrib</code>. Now, execute the
@@ -498,7 +499,7 @@ CREATE TABLE pgpool_catalog.dist_def (
<p>A distribution rule decides how to distribute data to a
particular node. Data will be distributed depending on the value of
-"col_name" column. "dist_def_func" is a function that takes the value
+the "col_name" column. "dist_def_func" is a function that takes the value
of "col_name" as its argument, and returns an integer which
points to the appropriate database node ID where the data should be
stored.</p>
@@ -510,7 +511,7 @@ nodes can be merged into one result.</p>
<h4><p>3.2.3. Defining replicate_def table</p></h4>
<p>
If you want to use replicated tables in SELECT in parallel mode, you
-need to register information of such tables(replication rule) to a table
+need to register information about such tables(replication rule) to a table
called replicate_def.
The replicate_def table has already been made when making it from the
system_db.sql file when dist_def is defined.
@@ -530,7 +531,7 @@ CREATE TABLE pgpool_catalog.replicate_def (
replicate_def includes table's meta data information(dbname, schema_name, table_name, col_list, type_list).
</p>
<p>
-All the query analysis and query rewriting process are depending on the
+All the query analysis and query rewriting process are dependent on the
information (table, column and type) stored in dist_def and/or
replicate_def table. If the information is not correct, analysis and
query rewriting process will produce wrong results.
@@ -543,7 +544,7 @@ sample data into three database nodes. The sample data will be created
by "pgbench -i -s 3" (i.e. scale factor of 3). We will create a new
database called "bench_parallel" for this section.</p>
-<p>In pgpool-II's source code, you can find
+<p>In pgpool-II's source code, you can find the
<code>dist_def_pgbench.sql</code> file in <code>sample</code>
directoy. We will use this sample file here to create distribution
rules for pgbench. Execute the following command in extracted
@@ -556,7 +557,7 @@ pgpool-II source code directory.</p>
<p>Inside <code>dist_def_pgbench.sql</code>, we are inserting one
row into "dist_def" table. There is a distribution
function for accounts table.
-For key-column, aid is defined for accounts respectively (which is primary keys)</p>
+For the key-column, aid is defined for accounts respectively (which is the primary keys)</p>
<pre>
INSERT INTO pgpool_catalog.dist_def VALUES (
@@ -570,7 +571,7 @@ INSERT INTO pgpool_catalog.dist_def VALUES (
);
</pre>
-<p>Now, we must define the distribution function for accounts table. Note
+<p>Now, we must define the distribution function for the accounts table. Note
that you can use the same function from different tables. Also, you
can define functions using languages other than SQL (e.g. PL/pgSQL,
PL/Tcl, etc.).</p>
@@ -581,7 +582,7 @@ The value of the aid is 1 to 300000.
The function is defined so that data is evenly distributed to three data base nodes.
</p>
<p>
-SQL function will be defined as the return of the number of the data base node.
+An SQL function will be defined as the return of the number of the data base node.
</p>
</p>
@@ -638,12 +639,12 @@ be restarted. Please refer to section "1.5 <a
href="#start-shutdown">Starting/Stopping pgpool-II</a>".</p>
<p>After configuring <code>pgpool.conf</code> and restarting
-pgpool-II, let's try and see if parallel query is working OK.</p>
+pgpool-II, let's try and see if parallel query is working.</p>
<p>First, we need to create a database to be distributed. We will name
it "bench_parallel". This database needs to be created on all the
-nodes. Use <code>createdb</code> commands through pgpool-II, and the
-database will be created on all the nodes.</p>
+nodes. Use the <code>createdb</code> commands through pgpool-II, and the
+databases will be created on all the nodes.</p>
<pre>$ createdb -p 9999 bench_parallel</pre>
[parent: 7a4b12c10a60]