Mon Oct 18 12:48:43 PDT 2010
- Previous message: [Slony1-general] Rejoin a master database to replication set.
- Next message: [Slony1-general] slony-I 1.2.20 replication lags behind when pg_dump is running ON THE SLAVE.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi. Replication lags over 5 minutes behind (sometimes over 10 minutes behind) while pg_dump is running on the slave. We monitor our replication lag using Bucardo's check_postgres.pl and it keeps showing up on the monitoring/alerting radar 4 times a day, when we do the pg_dump. I've increased the alert threshold to 30 minutes as an immediate measure, but is there any way to reduce pg_dump's impact on replication? or will we pretty much have to live with it? Best, -at
- Previous message: [Slony1-general] Rejoin a master database to replication set.
- Next message: [Slony1-general] slony-I 1.2.20 replication lags behind when pg_dump is running ON THE SLAVE.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list