Fri Sep 8 13:01:31 PDT 2006
- Previous message: [Slony1-general] adding tables to replication makes lag go away
- Next message: [Slony1-general] Slony-I 1.2 - RC4 status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sep 8, 2006, at 3:46 PM, Richard Yen wrote: > Also, I wonder if I'm overly-concerned about lag_time and > lag_num_events; I'm running a 3-node system where all SELECTS go to > the 2 subscribers and all data changes go to the provider. > Naturally, I'd want all the data to be synced ASAP, so that users > don't get confused. I'm talking about data like contact info, > timestamps, etc. Right now, I get warning messages when we hit 40 > lag_num_events or 60 sec lag_time, whichever comes first. > > Any insights? it is *asynchronous* replication, so there will always be some delay. The amount of delay you can tolerate depends on your business requirements, and nobody else can decide that for you. If 60 seconds is what you need, then surely set off alarms when it gets that high. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2530 bytes Desc: not available Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20060908/4b5de1f1/attachment.bin
- Previous message: [Slony1-general] adding tables to replication makes lag go away
- Next message: [Slony1-general] Slony-I 1.2 - RC4 status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list