I have the following setup in my conf file:

cleanup_interval="5 seconds"
sync_interval=1000

cluster_name='dbcluster01'
conn_info='...'

And, via the log, it looks like slony is picking up on the 5 second cleanup
interval:

2014-09-15 09:31:40 EDT CONFIG main: String option pid_file = [NULL]
2014-09-15 09:31:40 EDT CONFIG main: String option archive_dir = [NULL]
2014-09-15 09:31:40 EDT CONFIG main: String option sql_on_connection =
[NULL]
2014-09-15 09:31:40 EDT CONFIG main: String option lag_interval = [NULL]
2014-09-15 09:31:40 EDT CONFIG main: String option command_on_logarchive =
[NULL]
2014-09-15 09:31:40 EDT CONFIG main: String option syslog_facility = LOCAL0
2014-09-15 09:31:40 EDT CONFIG main: String option syslog_ident = slon
2014-09-15 09:31:40 EDT CONFIG main: String option cleanup_interval = 5
seconds

However, it only actually runs cleanup about every 10 minutes (the default):

NOTICE:  Slony-I: log switch to sl_log_1 complete - truncate sl_log_2
CONTEXT:  PL/pgSQL function _dbcluster01.cleanupevent(interval) line 94 at
assignment
2014-09-18 06:28:40 EDT INFO   cleanupThread:    0.368 seconds for
cleanupEvent()
NOTICE:  Slony-I: Logswitch to sl_log_2 initiated
CONTEXT:  SQL statement "SELECT "_dbcluster01".logswitch_start()"
PL/pgSQL function _dbcluster01.cleanupevent(interval) line 96 at PERFORM
2014-09-18 06:39:27 EDT INFO   cleanupThread:    0.018 seconds for
cleanupEvent()
NOTICE:  Slony-I: log switch to sl_log_2 complete - truncate sl_log_1
CONTEXT:  PL/pgSQL function _dbcluster01.cleanupevent(interval) line 94 at
assignment
2014-09-18 06:51:10 EDT INFO   cleanupThread:    0.106 seconds for
cleanupEvent()
2014-09-18 06:51:10 EDT INFO   cleanupThread:    0.006 seconds for vacuuming
NOTICE:  Slony-I: Logswitch to sl_log_1 initiated
CONTEXT:  SQL statement "SELECT "_dbcluster01".logswitch_start()"
PL/pgSQL function _dbcluster01.cleanupevent(interval) line 96 at PERFORM
2014-09-18 07:01:52 EDT INFO   cleanupThread:    0.016 seconds for
cleanupEvent()
NOTICE:  Slony-I: log switch to sl_log_1 complete - truncate sl_log_2
CONTEXT:  PL/pgSQL function _dbcluster01.cleanupevent(interval) line 94 at
assignment
2014-09-18 07:13:33 EDT INFO   cleanupThread:    0.110 seconds for
cleanupEvent()
NOTICE:  Slony-I: Logswitch to sl_log_2 initiated
CONTEXT:  SQL statement "SELECT "_dbcluster01".logswitch_start()"
PL/pgSQL function _dbcluster01.cleanupevent(interval) line 96 at PERFORM
2014-09-18 07:24:46 EDT INFO   cleanupThread:    0.014 seconds for
cleanupEvent()
2014-09-18 07:24:46 EDT INFO   cleanupThread:    0.006 seconds for vacuuming
NOTICE:  Slony-I: log switch to sl_log_2 complete - truncate sl_log_1
CONTEXT:  PL/pgSQL function _dbcluster01.cleanupevent(interval) line 94 at
assignment
2014-09-18 07:36:17 EDT INFO   cleanupThread:    0.114 seconds for
cleanupEvent()
NOTICE:  Slony-I: Logswitch to sl_log_1 initiated
CONTEXT:  SQL statement "SELECT "_dbcluster01".logswitch_start()"
PL/pgSQL function _dbcluster01.cleanupevent(interval) line 96 at PERFORM
2014-09-18 07:47:31 EDT INFO   cleanupThread:    0.018 seconds for
cleanupEvent()

In order to perform the upgrade to the latest version, it says I need to
set this interval low to clear up any data in the log tables, but I'm stuck
trying to get that to happen.

Any ideas?


Kristopher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20140919/9d3076c1/attachment.htm