Wed Feb 20 12:34:51 PST 2008
- Previous message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Next message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Feb 20, 2008 at 11:55 AM, Geoffrey <lists at serioustechnology.com> wrote: > I simply don't understand how one table inparticular could get so far > out of sync. We're talking 300 records. Have you checked that replication is up to date (look at the sl_status view on the master)? What do the slon logs say? Post them up using pastbin or something for review. > Is it possible I should be tweaking the configuration in some way? I > see a default value for SYNC_CHECK_INTERNAL. Is 1000 a good value? The default values are usually fine. 1000 is fine for sync check interval, though a bit overkill for most scenarios, the default of 2000 is usually OK. -Dave
- Previous message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Next message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list