[Slony1-general] Connections increase when upgrading to slony 2.2.7

2019-02-27 Thread SAS
Hello, We have a slony cluster with 11 nodes, and 3 sets. All PostgreSQL servers are still running a 9.2.x version. The upgrade of Slony is part of the PostgreSQL nodes upgrades, as we have to run a more recent version, so as to be able to insert PG 11 nodes in the cluster. The replication

Re: [Slony1-general] Connections increase when upgrading to slony 2.2.7

2019-03-05 Thread SAS
Le 02/03/2019 à 02:57, Steve Singer a écrit : > On Wed, 27 Feb 2019, SAS wrote: > > If you don't have paths between two nodes then there won't be a connection > between them. > > If your not going to have a complete network of paths then you should > consider failure cases in

Re: [Slony1-general] Connections increase when upgrading to slony 2.2.7

2019-03-05 Thread SAS
Le 05/03/2019 à 13:22, Steve Singer a écrit : > On Tue, 5 Mar 2019, SAS wrote: > >> Thank you for your answer. >> >> I could easily drop some paths, and then lower the number of established >> connections on some >> nodes. >> >> Could you point me

Re: [Slony1-general] upgrading from 9.4 to 11.5

2019-11-12 Thread SAS
Hello, Le 12/11/2019 à 16:24, Mark Steben a écrit : > Good morning, > We are a former user of slony and are looking to perform an upgrade from an > on-prem linux server (9.4) to Azure (11.5)  Can we use slony to set up master > (9.4) to slave (11.5) or is that too big a jump?     > > A prompt

Re: [Slony1-general] Is slony 2.2.4 compatible with OSS 9.5.21?

2020-03-25 Thread SAS via Slony1-general
Le 25/03/2020 à 03:37, Rajni Baliyan via Slony1-general a écrit : > Hello folks, > > I need some pointers and recommendations regarding Slony and PostgreSQL > minor/major version upgrade. > > Is there any document/link where I can see Slony version compatibility matrix > with PostgreSQL

Re: [Slony1-general] Replication cascade with 2 differents replications on the same table

2021-05-26 Thread SAS via Slony1-general
Le 26/05/2021 à 14:51, Sebastien Marchand via Slony1-general a écrit : > > Hi, > > thank you, but i don't know how do this, my server A can't talk to my server > C... > Hello, If I understand well, A can talk to B, and B can talk to C. You should configure sl_path (or use Slonik STORE PATH) to

Re: [Slony1-general] Replication cascade with 2 differents replications on the same table

2021-05-27 Thread SAS via Slony1-general
Le 27/05/2021 à 10:05, Sebastien Marchand via Slony1-general a écrit : > Hi, > > I will try this today. > > I can move slon from A to B too no ? Result, 2 slon on B , one on C and no > one on A. > > Thank you all > You can have your 3 slon daemons running on B, which can see all nodes, indeed.

Re: [Slony1-general] Nodes awaiting actions

2024-02-13 Thread SAS via Slony1-general
Le 17/01/2024 à 10:47, Andy Dossett via Slony1-general a écrit : Hi How do I determine from the master node tables which slave nodes are yet to process the data on the sl_log tables? Thanks Andy ___ Slony1-general mailing list