Tue Oct 19 07:18:09 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 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.
- 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