Mon Sep 22 07:58:35 PDT 2014
- Previous message: [Slony1-general] Compiling Slony 1.2.23 for Postgres 9.3.4
- Next message: [Slony1-general] Slony ignoring cleanup_interval?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Message: 1 > Date: Fri, 19 Sep 2014 16:55:47 -0400 > From: Steve Singer <ssinger at ca.afilias.info> > Subject: Re: [Slony1-general] Slony ignoring cleanup_interval? > To: Kristopher <kristopherwilson at gmail.com>, > slony1-general at lists.slony.info > Message-ID: <541C9853.3000307 at ca.afilias.info> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 09/19/2014 01:50 PM, Kristopher wrote: >> 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): >> > We seem to be using > #define SLON_CLEANUP_SLEEP 600 /* sleep 10 minutes between */ > > as basis to a random time to sleep between calling the cleanup process. > We then pass the cleanup_interval from config file to the stored > function. > > Maybe Jan or Chris can comment if they remember how this was intended to > work with a cleanup_interval that is specified in the config file. > > > > For purposes of your upgrade you want to make sure that sl_log_1 and > sl_log_2 have no rows in them then you can upgrade. > I encountered the same problem while upgrading. You can workaround it by running a: select _your_schema.cleanupevent('5 seconds'::interval); until sl_log[12] are empty. Regards, Ger -- Ger Timmens Adyen - Payments Made Easy http://www.adyen.com Visiting Address: Kantoorgebouw Nijenburg Mail Address: Simon Carmiggeltstraat 6-50, 5th floor P.O. Box 10095 1011 DJ Amsterdam 1001 EB Amsterdam The Netherlands The Netherlands Direct +31.20.240.1248 Office +31.20.240.1240 Mobile +31.62.483.8468 Email ger.timmens at adyen.com
- Previous message: [Slony1-general] Compiling Slony 1.2.23 for Postgres 9.3.4
- Next message: [Slony1-general] Slony ignoring cleanup_interval?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list