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