Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bB1x2-0003DA-4h for pgsql-performance@arkaria.postgresql.org; Thu, 09 Jun 2016 15:32:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bB1x1-0002Un-Im for pgsql-performance@arkaria.postgresql.org; Thu, 09 Jun 2016 15:32:55 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bB1x0-0002UO-Ns for pgsql-performance@postgresql.org; Thu, 09 Jun 2016 15:32:54 +0000 Received: from nm17-vm4.bullet.mail.ir2.yahoo.com ([212.82.96.219]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bB1ws-0000pr-VU for pgsql-performance@postgresql.org; Thu, 09 Jun 2016 15:32:53 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048; t=1465486363; bh=FqK5iU435vOWQQbFActZZPXOowkQ/FRKSipnCEJoClo=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=kzjtZ94iS2ZZ/FxvUY4uiL2lc4k5zx94eMdRex+WAwl1nmj2SFzAGIBinNZx6puz1TUMtBvo7JWrQLw4KQgDTO/5tvrKXVSWFrgVE3hRlaQ08c52hOJ72YnkgZqudS5yBiA+a6jK5FZTc6YFmo3pdPsH+ZS4bYUwx+WKVL61OVAmtj/I2mXx5IHIdAphhlt6HW91562Ecyh40O6EbSD2cHzSxyNuYu7G2MZrekEsFoPdDutz2EbK9V2ANrEmekKOJ/bD/KFYRjDcEzeFcrIC2mheNY41pWMHx0iGnYENFwhmHoK/7VknKQmvN4s9GNKHuY+nBe3e8DYU+s5fx+lKhg== Received: from [212.82.98.48] by nm17.bullet.mail.ir2.yahoo.com with NNFMP; 09 Jun 2016 15:32:43 -0000 Received: from [212.82.98.106] by tm1.bullet.mail.ir2.yahoo.com with NNFMP; 09 Jun 2016 15:32:43 -0000 Received: from [127.0.0.1] by omp1043.mail.ir2.yahoo.com with NNFMP; 09 Jun 2016 15:32:43 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 967109.62171.bm@omp1043.mail.ir2.yahoo.com X-YMail-OSG: b54ECDMVM1nX3kOzfaNa.4ohoL2lEcIrdPVaDsi2ana2_GxccdwwKs07drnEOcT P.riHEBhkfT0KU7WQojzETQR0mxKLhCqegaTYJh1Az.2vZLmmajpJtBqZLU8Dj354Pb6RBljMNlh qA0jTIaliHKpvQGr_TvcOX4M8RSJ7qZf_oK2Yoc7DmtDK9BXmyQxEo.uFZvmDMr6dy.a3eBu.dYy raQpL.QLBVHagb3zqtclDNcQG84XT6Q7.rgpncGoAn0JBaC5NnmvRF_4RHKlWkARIFU.zwMSsMaC CXsWx.rawCB3Y1UVyLn0wBsZyx0vPv984LXtdURbWnFKiNshwww0cEheN_svaU8oBY3h9OTD6dZg B9ggCz6opIfau09CuYmuIPNAY_.ISSYgUbZj8R2Ff6CUDjcjQa5E_EkVCU8ihXGenKBpOGCoR2Lt Ytt7q9ugJfqVhbftBwxC2q5iC6Nb_SYVn5fPqoLOskfObpSVpX6q46.Vcxp732idunqGXP9uwhv9 DX2JNSTe1nbRkHdGD Received: from jws11150.mail.ir2.yahoo.com by sendmailws162.mail.ir2.yahoo.com; Thu, 09 Jun 2016 15:32:43 +0000; 1465486363.191 Date: Thu, 9 Jun 2016 15:32:42 +0000 (UTC) From: Glyn Astill Reply-To: Glyn Astill To: avi Singh , "pgsql-performance@postgresql.org" Message-ID: <1879732441.636578.1465486362833.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: References: Subject: Re: slony rpm help slony1-95-2.2.2-1.rhel6.x86_64 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Length: 1126 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org > From: avi Singh >To: pgsql-performance@postgresql.org >Sent: Saturday, 4 June 2016, 0:03 >Subject: [PERFORM] slony rpm help slony1-95-2.2.2-1.rhel6.x86_64 > > > >Hi All > Can anyone please point me to location from where i can get slony slony1-95-2.2.2-1.rhel5.x86_64 rpm. I'm upgrading database from version 9.3 to 9.5. Current version of rpm we are using is slony1-93-2.2.2-1.el5.x86_64 and the one that is available on postgresql website for 9.5 is slony1-95-2.2.4-4.rhel5.x86_64 which is not compatible and throws an error when i test the upgrade. In the past i was able to find the 2.2.2-1 version rpm for previous versions on postgres website but not this time for postgresql 9.5 > > What you'd be better off doing is installing Slony 2.2.4 on all your servers (or better a 2.2.5) rather than trying to get the older version. If you can't get a package you could compile Slony yourself. The not compatible error you mention is most likely because you've failed to update the Slony functions. See: http://slony.info/documentation/2.2/stmtupdatefunctions.html Glyn -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance