Tue Mar 21 18:40:54 PST 2006
- Previous message: [Slony1-general] Slon not catching up
- Next message: [Slony1-general] Slon not catching up
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> when you fall way behind (say, a few million rows in sl_log_1) you're > starting to ask your system to do more work per unit of time than it > can. even if you can stop updating the origin db, you may not catch > up in a timely fashion. it is best to punt and restart the > replication as you did. what if the sl_log_1 is empty and the sl_event contains some 100,000 records? i did experiment with few option but couldn't clear it for 2 days. it would go to 93,000 and then just climb back up, connectivity was fine. l
- Previous message: [Slony1-general] Slon not catching up
- Next message: [Slony1-general] Slon not catching up
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list