From b5995955c9a727a3140f855b51029d39183eac81 Mon Sep 17 00:00:00 2001
From: Tatsuo Ishii
+There is some restrictions of using SQL via pgpool-II. +See Restrictions for more details. +
If you are using PostgreSQL 7.3 or before, there are some restrictions of functionalities of pgpool-II.
+ +Also you must make sure that all of PostgreSQL servers's major versions are identical. +In addition this, hardware architectures and OSs must be identical if you want to use online recovery. +
+The source code of pgpool-II can be downloaded from: +href="http://pgfoundry.org/projects/pgpool/">pgpool development page
+ +Installing pgpool-II from source code requires gcc 2.9 or higher, and GNU
make. Also, pgpool-II links libpq library, so the libpq library and development
headers must be installed on a machine used to build pgpool-II. Additionally
@@ -156,7 +174,7 @@ installed. Default value is obtained by pg_config
make
make install
-will install pgpool-II. (If you use FreeBSD, replace make with gmake)
+will install pgpool-II. (If you use Solaris or FreeBSD, replace make with gmake)
+
pcp.confpgpool-II provides the control interface where an administrator @@ -304,12 +333,7 @@ cp $prefix/etc/pgpool.conf.sample $prefix/etc/pgpool.conf An empty line or a line starting with "#" is treated as a comment and will be ignored.
-In the raw mode, clients simply connect to the PostgreSQL servers -via pgpool-II. This mode is useful for simply limiting excess -connections to the servers, or enabling failover with multiple -servers.
+In the connection pool mode, all functions in raw mode and the connection pool function can be used. To enable this mode, set @@ -814,7 +838,7 @@ You need to re-read pgpool.conf upon modification of this direrctive.
Failover in the connection pool mode is the same as in the raw mode.
-This mode enables data replication between the backends. The configuration parameters below must be set in addtion to everything above.
@@ -836,7 +860,7 @@ configuration parameters below must be set in addtion to everything above.When set to true, if a backend returns number of affected - tuples by UPDATE/DELETE + tuples by INSERT/UPDATE/DELETE different between the backends, the backends that differ from most frequent result set are degenerated. If set to false, the session is terminated and the backends are not @@ -859,6 +883,35 @@ configuration parameters below must be set in addtion to everything above.
degenerated. Default is false.+Specify comma separated function name list, those do not update database. +SELECTs use functions not specified in this list are not load balanced, replicated if in replication mode. +In master slave mode, SELECTs are sent to master(primary) only. +
+ + ++Specify comma separated function name list, those do update database. +SELECTs use functions specified in this list are not load balanced, replicated if in replication mode. +In master slave mode, SELECTs are sent to master(primary) only. +
++You should not make those lists nonempty at the same time. +
++Prior to pgpool-II 3.0, nextval() and setval() are the functions those do writes to database. +You can emulate this by using white_function_list and black_function_list: +
++white_function_list = '' +black_function_list = 'upper,lower' ++
This mode is for using pgpool-II with another master/slave replication software (like Slony-I and Streaming replication), so it really does the actual data -- 2.39.5