Write correct boolean value for exceede lag, rather than just the lag in seconds.

[slony-i/pgbouncer_follower] / pgbouncer_follower_rw.conf

diff --git a/pgbouncer_follower_rw.conf b/pgbouncer_follower_rw.conf
index f06fa446bd8c31c26f419d70bc86411d024d4e13..79688bbf8f5883a9f9107af49b44754a1fda4570 100755 (executable)
--- a/pgbouncer_follower_rw.conf
+++ b/pgbouncer_follower_rw.conf
@@ -1,16 +1,21 @@
 #------------------------------------------------------------------------------
-# Slony cluster information
+# Replication cluster information
 #------------------------------------------------------------------------------
-slony_user=slony                                                                # Username to use when connecting to PostgreSQL server to 
-                                                                                # retrieve slony cluster configuration
+replication_method=slony                                                       # Possible values 'slony' or 'wal'
 
-slony_pass=                                                                     # Password for above, leave blank to use .pgpass
+replication_user=repuser                                                        # Username to use when connecting to PostgreSQL server to 
+                                                                                # retrieve slony cluster configuration / streaming rep state
+
+replication_pass=                                                               # Password for above, leave blank to use .pgpass
 
 slony_cluster_name=test_replication                                             # Slony-I replication cluster name
 
-server_conninfo=dbname=TEST host=localhost port=5432                            # Conninfo of server to to retrieve slony cluster configuration
-server_conninfo=dbname=TEST host=localhost port=5433                            # from, accepts multiple servers and will try in order given.
-server_conninfo=dbname=TEST host=localhost port=5434
+#------------------------------------------------------------------------------
+# Server information
+#------------------------------------------------------------------------------
+server_conninfo=dbname=TEST host=localhost port=5432                            # Conninfo of servers.  For slony this list is used to pull cluster
+server_conninfo=dbname=TEST host=localhost port=5433                            # configuration from the first contactable node so all nodes not necessarily
+server_conninfo=dbname=TEST host=localhost port=5434                            # not necessarily required. For WAL replication all servers required.
 server_conninfo=dbname=TEST host=localhost port=5435
 
 #------------------------------------------------------------------------------
@@ -22,8 +27,9 @@ follower_poll_interval=5000
 slony_sets_to_follow=all                                                        # Comma separated list of set id's to follow E.g. "1,2,3,4" or "all"
 
 only_follow_origins=true                                                        # If true pgbouncer will only be reconfigured and reloaded
-                                                                                # when the origin of a set moves. If false any changes to origins,
-                                                                                # providers or subscribers will initiate a reconfigure and reload.
+                                                                                # when the origin of a set / primary moves. If false any 
+                                                                                # changes to origins, providers or subscribers will initiate 
+                                                                                # a reconfigure and reload.
 
 pool_mode=rw                                                                    # Values are rw/ro. "rw" follows the origin node
                                                                                 # whereas "ro" will follow a subscriber  of the sets
@@ -31,10 +37,13 @@ pool_mode=rw
 
 pool_all_databases=false                                                        # If true uses a wildcard in the conninfo for the pooler
                                                                                 # thus hosting all databases on the node. If false
-                                                                                # only the replicated database is hosted.
+                                                                                # only the database in the target servers conninfo is hosted.
+
+auth_user=                                                                      # If set auth_user will be appended to conninfo written
+                                                                                # in [databases] section.
 
-status_file=/var/slony/pgbouncer_follower/pgbouncer_follower_%mode.status       # File used to store tate of the cluster
-log_file=/var/slony/pgbouncer_follower/pgbouncer_follower_%mode.log             # Log for pool_follower script
+status_file=/var/run/pgbouncer_follower_%mode.status                            # File used to store tate of the cluster
+log_file=/var/log/pgbouncer_follower_%mode.log                                  # Log for pool_follower script
 pid_file=/var/run/pgbouncer_follower_%mode.pid                                  # Pidfile for poll mode 
 pool_conf_template=/etc/pgbouncer/pgbouncer_%mode.template                      # Template configuration file
 pool_conf_target=/etc/pgbouncer/pgbouncer_%mode.ini                             # Target configuration file to be modified
@@ -43,5 +52,5 @@ pool_reload_command=/etc/init.d/pgbouncer_%mode restart
                                                                                 # pool_conf_target and pool_reload_command parameters:
                                                                                 #   %mode - Pool Mode
                                                                                 #   %clname - Slony cluster name
-max_ro_lag=0                                                                    # Maximum lag in seconds allowed for subscriber nodes when 
+max_ro_lag=0                                                                    # Maximum lag in seconds allowed for subscriber nodes when
                                                                                 # running in ro mode. 0 = don't monitor lag.