Kevin Kempter <kevink at consistentstate.com> writes:
> Is there a way to control how often a slave checks the master for updates ?

Yes, this is controllable, via the parameters listed here:
   http://slony.info/documentation/slon-config-interval.html

sync_interval and sync_interval_timeout are the usual parameters to
use to tune this.

These may be controlled either via using a config file for the slons,
or via a command line parameter.

-s SYNC check interval

    The sync_interval, measured in milliseconds, indicates how often
    slon should check to see if a SYNC should be introduced. Default
    is 2000 ms. The main loop in sync_Thread_main() sleeps for
    intervals of sync_interval milliseconds between iterations.

-t SYNC interval timeout

    At the end of each sync_interval_timeout timeout period, a SYNC
    will be generated on the "local" node even if there has been no
    replicable data updated that would have caused a SYNC to be
    generated.

    If application activity ceases, whether because the application is
    shut down, or because human users have gone home and stopped
    introducing updates, the slon will iterate away, waking up every
    sync_interval milliseconds, and, as no updates are being made, no
    SYNC events would be generated. Without this timeout parameter, no
    SYNC events would be generated, and it would appear that
    replication was falling behind.
-- 
output = ("cbbrowne" "@" "linuxdatabases.info")
http://linuxfinances.info/info/internet.html
PALM BEACH COUNTY: We put the "duh" in Florida.