Sl_subscribe of my test : sub_set;sub_provider;sub_receiver;sub_forward;sub_active 1;1;2;FALSE;TRUE 1;1;130;FALSE;TRUE
Sl_path : pa_server;pa_client;pa_conninfo 1;2;dbname=DB host=192.168.0.29 port=5432 user=slony password=123;10 1;130;dbname=DB host=192.168.0.29 port=5432 user=slony password=123;10 2;1;dbname=DB host=192.168.0.3 port=5432 user=slony password=123;10 130;1;dbname=DB host=192.168.0.230 port=5432 user=slony password=123;10 Sub_forward true or false change nothing... Thx for your help. -----Message d'origine----- De : Steve Singer [mailto:st...@ssinger.info] Envoyé : jeudi 19 juillet 2018 05:42 À : Sébastien Marchand Cc : slony1-general@lists.slony.info Objet : Re: [Slony1-general] Problème with sl_listen and too many nodes On Wed, 18 Jul 2018, Sébastien Marchand wrote: What is sl_subscribe? (I assume sl_path has paths between each node) > > Hello, > > > > I have a problem with the sl_listen table. > > I have a replication that has been running for a very long time from a master to X slaves (1 master > node for 18 nodes) > > My concern comes from the sl_listen table which instead of just containing what it needs it creates > all the possible combinations. > > For example I have a test for 1 master and 2 slaves and I have 4 too many lines that are useless > for me: > > > > SL_LISTEN table > > origin; provider; receiver > > 1, 1, 2 > > 1; 1; 130 > > 2; 1; 130 > > 2; 2; 1 > > 2; 130; 1 > > 130, 1, 2 > > 130, 2, 1 > > 130; 130; 1 > > > > Here after cleaning what should be: > > > > origin; provider; receiver > > 1, 1, 2 > > 1; 1; 130 > > 2; 2; 1 > > 130; 130; 1 > > > > The problem is that with each add / delete of tables / nodes the table is re-filled again and I > have to redo the cleaning. > > > > My final question is: Is it normal for all nodes to talk to each other? > > > > Thank you. > > > _______________________________________________ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general
