Mon Nov 15 22:39:38 PST 2010
- Previous message: [Slony1-general] how to troubleshoot slony replication lag?
- Next message: [Slony1-general] how to troubleshoot slony replication lag?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Nov 15, 2010 at 9:49 AM, Steve Singer <ssinger at ca.afilias.info> wrote: > > It sounds to me like your transaction rate is too high for your setup. ... > Based on > your other post it sounds like the slave is having problems keeping up. Are > your master + slave a similar hardware configuration? Identical. And you hit the nail right on the head about the transaction rate being too high, I got the bottom of it, one of our application sub-modules was generating orders of magnitude more inserts/deletes than we expected -- brought this to light using pgstatspack, very handy. We dropped that one table from replication (we could do that) and very quickly replication lag went to near zero. Yay!! :) Thanks very much for the clear explanation of the sync event id's in the Slony logs and all your big help! Very much appreciated! Yours truly, Aleksey
- Previous message: [Slony1-general] how to troubleshoot slony replication lag?
- Next message: [Slony1-general] how to troubleshoot slony replication lag?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list