Tue Nov 9 11:45:58 PST 2010
- Previous message: [Slony1-general] Sl_log table is huge, over 100 million rows
- Next message: [Slony1-general] Sl_log table is huge, over 100 million rows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Here is the result: 1;3;10917446;"2010-11-09 11:43:11.552822";10306542;"2010-10-19 16:52:12.919763";"2010-10-19 16:52:06.15117";610904;"20 days 19:51:08.936181" 1;4;10917446;"2010-11-09 11:43:11.552822";10641537;"2010-11-09 12:50:41.670451";"2010-10-30 23:12:54.809831";275909;"9 days 13:30:20.27752" 1;2;10917446;"2010-11-09 11:43:11.552822";10641538;"2010-11-09 11:40:48.698673";"2010-10-30 23:13:00.813928";275908;"9 days 13:30:14.273423" how do i check if the son daemons are running? Vick Khera wrote: > > On Tue, Nov 9, 2010 at 1:54 PM, sharadov <sreddy at spark.net> wrote: >> >> >> We have slony replication set up, and the replication on the slave has >> fallen behind by 10 days. On investigating I noticed that the sl_log_1 >> table >> has 25K records, but the sl_log_2 table has over 100 million rows, and >> they >> keep going up. How do I go about troubleshooting this? > > What is the output of > > select * from _XXX.sl_status; > > on your master node, where XXX is the cluster name? > > are the slon daemons running? > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general > > -- View this message in context: http://old.nabble.com/Sl_log-table-is-huge%2C-over-100-million-rows-tp30173901p30174341.html Sent from the Slony-I -- General mailing list archive at Nabble.com.
- Previous message: [Slony1-general] Sl_log table is huge, over 100 million rows
- Next message: [Slony1-general] Sl_log table is huge, over 100 million rows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list