Tue Oct 19 10:00:39 PDT 2010
- Previous message: [Slony1-general] slony-I 1.2.20 replication lags behind when pg_dump is running ON THE SLAVE.
- 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 ]
On Oct 19, 2010, at 8:18 AM, Vick Khera wrote: > On Mon, Oct 18, 2010 at 3:48 PM, Aleksey Tsalolikhin > <atsaloli.tech at gmail.com> wrote: >> 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? >> > > Your hardware is approaching the limits of the workload you are > throwing at it. I'd recommend adding more RAM and/or tuning postgres > to use more of it somehow. Either that or faster disks, or both. > I think the problem is actually the exclusive lock mentioned in the previous post. Upgrading hardware might make the dump run faster, but it will still block replication. We've noticed the exact same thing on our systems.
- Previous message: [Slony1-general] slony-I 1.2.20 replication lags behind when pg_dump is running ON THE SLAVE.
- 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