1
# $Id: slon.conf-sample,v 1.6.2.2 2007-08-08 15:23:30 cbbrowne Exp $
3
# Sets how many cleanup cycles to run before a vacuum is done.
4
# Range: [0,100], default: 3
7
# Debug log level (higher value ==> more output). Range: [0,4], default 4
10
# Check for updates at least this often in milliseconds.
11
# Range: [10-60000], default 2000
14
# Maximum amount of time in milliseconds before issuing a SYNC event,
15
# This prevents a possible race condition in which the action sequence
16
# is bumped by the trigger while inserting the log row, which makes
17
# this bump is immediately visible to the sync thread, but
18
# the resulting log rows are not visible yet. If the sync is picked
19
# up by the subscriber, processed and finished before the transaction
20
# commits, this transaction's changes will not be replicated until the
21
# next SYNC. But if all application activity suddenly stops,
22
# there will be no more sequence bumps, so the high frequent -s check
23
# won't detect that. Thus, the need for sync_interval_timeout.
24
# Range: [0-120000], default 10000
25
#sync_interval_timeout=10000
27
# Maximum number of SYNC events to group together when/if a subscriber
28
# falls behind. SYNCs are batched only if there are that many available
29
# and if they are contiguous. Every other event type in between leads to
30
# a smaller batch. And if there is only one SYNC available, even -g60
31
# will apply just that one. As soon as a subscriber catches up, it will
32
# apply every single SYNC by itself.
33
# Range: [0,100], default: 6
36
# Size above which an sl_log_? row's log_cmddata is considered large.
37
# Up to 500 rows of this size are allowed in memory at once. Rows larger
38
# than that count into the sync_max_largemem space allocated and free'd
40
# Range: [1024,32768], default: 8192
41
#sync_max_rowsize=8192
43
# Maximum amount of memory allowed for large rows. Note that the algorithm
44
# will stop fetching rows AFTER this amount is exceeded, not BEFORE. This
45
# is done to ensure that a single row exceeding this limit alone does not
47
# Range: [1048576,1073741824], default: 5242880
48
#sync_max_largemem=5242880
50
# If this parameter is 1, messages go both to syslog and the standard
51
# output. A value of 2 sends output only to syslog (some messages will
52
# still go to the standard output/error). The default is 0, which means
54
# Range: [0-2], default: 0
57
# If true, include the process ID on each log line. Default is false.
60
# If true, include the timestamp on each log line. Default is true.
63
# A strftime()-conformant format string for use with log timestamps.
64
# Default is '%Y-%m-%d %H:%M:%S %Z'
65
#log_timestamp_format='%Y-%m-%d %H:%M:%S %Z'
67
# Where to write the pid file. Default: no pid file
68
#pid_file='/path/to/your/pidfile'
70
# Sets the syslog "facility" to be used when syslog enabled. Valid
71
# values are LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7.
72
#syslog_facility=LOCAL0
74
# Sets the program name used to identify slon messages in syslog.
77
# Set the cluster name that this instance of slon is running against
78
# default is to read it off the command line
79
#cluster_name='sloncluster'
81
# Set slon's connection info, default is to read it off the command line
82
#conn_info='host=/tmp port=5432 user=slony'
84
# maximum time planned for grouped SYNCs
85
# If replication is behind, slon will try to increase numbers of
86
# syncs done targetting that they should take this quantity of
87
# time to process. in ms
88
# Range [10000,600000], default 60000.
89
#desired_sync_time=60000
91
# Execute the following SQL on each node at slon connect time
92
# useful to set logging levels, or to tune the planner/memory
93
# settings. You can specify multiple statements by separating
95
#sql_on_connection="SET log_min_duration_statement TO '1000';"
97
# Command to run upon committing a log archive.
98
# This command is passed one parameter, namely the full pathname of
100
#command_on_logarchive="/usr/local/bin/movearchivetoarchive"
102
# A PostgreSQL value compatible with ::interval which indicates how
103
# far behind this node should lag its providers.
104
# lag_interval="8 minutes"
106
# Directory in which to stow sync archive files
107
# archive_dir="/tmp/somewhere"