Connection settings

2. Connection settings

cluster_name (string)

Set the cluster name that this instance of slon is running against. The default is to read it off the command line.

conn_info (string)

Set slon's connection info; default is to read it off the command line.

sql_on_connection (string)

Execute this SQL on each node at slon connect time. Useful to set logging levels, or to tune the planner/memory settings. You can specify multiple statements by separating them with a ;

tcp_keepalive (bool)

Enables sending of TCP KEEP alive requests between slon and the PostgreSQL backends. Defaults to true.

tcp_keepalive_idle (integer)

The number of seconds of idle activity after which a TCP KEEPALIVE will be sent across the network. The tcp_keepalive parameter must be enabled for this to take effect. The default value is 0 which means use the operating systems default. Setting this parameter has no effect on Win32 systems.

tcp_keepalive_count ( integer)

The number of keep alive requests to the server that need to be lost before the connection is declared dead. tcp_keep_alive must be turned on for this parameter to take effect. The default value is 0 which means use the operating systems default. Setting this parameter has no effect on Win32 systems.

tcp_keepalive_interval (integer)

The number of seconds between TCP keep alive requests. tcp_keepalive must be enabled for this parameter to take effect. The default value is 0 which means use the operating systems default. Setting this parameter has no effect on Win32 systems.

remote_listen_serializable_transactions (integer)

Sets if the remote_listen connection should use read only serializable deferrable transactions(true) or read only repetable read transactions(false). The default setting is true. This allows postgresql to defer the start of a transaction to avoid serialization issues. Repeatable read transactions will provide less locking contention for some workloads.

enable_version_check (integer)

Sets if slon should check the slony version used in each database. Slon normally requires that all nodes have the exact same version of slony installed. When this setting is true (the default) slon will check this when it establishes a connection to a database. Set this to false to disable checking of the version. When this setting is false users are responsible for determining if the different versions of slony they have instaled are compatible with each other.