Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z7o5J-0003bc-Q4 for pgsql-admin@arkaria.postgresql.org; Wed, 24 Jun 2015 17:03:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1Z7o5H-0000CI-LP for pgsql-admin@arkaria.postgresql.org; Wed, 24 Jun 2015 17:03:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1Z7o4y-0008JU-TU for pgsql-admin@postgresql.org; Wed, 24 Jun 2015 17:03:16 +0000 Received: from imx6.etecsa.cu ([200.55.152.141]) by magus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1Z7o4s-0003NC-U5 for pgsql-admin@postgresql.org; Wed, 24 Jun 2015 17:03:15 +0000 Received: from mn1.etecsa.cu (unknown [192.168.91.41]) by imx6.etecsa.cu (Postfix) with ESMTP id 23E5B117 for ; Wed, 24 Jun 2015 13:01:46 -0400 (CDT) Received: (qmail 10450 invoked by uid 11187); 24 Jun 2015 18:02:47 -0000 Received: from 192.168.91.6 by mn1.etecsa.cu (envelope-from , uid 502) with qmail-scanner-2.08 (spamassassin: 3.2.5. Clear:RC:1(192.168.91.6):. Processed in 0.019176 secs); 24 Jun 2015 18:02:47 -0000 Received: from unknown (HELO webmail.etecsa.cu) ([192.168.91.6]) (envelope-sender ) by mn2.etecsa.cu (qmail-ldap-1.03) with SMTP for ; 24 Jun 2015 18:02:47 -0000 Received: from 192.168.207.54 (SquirrelMail authenticated user gilberto.castillo) by webmail.etecsa.cu with HTTP; Wed, 24 Jun 2015 13:02:47 -0500 (GMT+5) Message-ID: <39343.192.168.207.54.1435168967.squirrel@webmail.etecsa.cu> In-Reply-To: References: <37952.192.168.207.54.1435162036.squirrel@webmail.etecsa.cu> <37964.192.168.207.54.1435162661.squirrel@webmail.etecsa.cu> <37991.192.168.207.54.1435164476.squirrel@webmail.etecsa.cu> <39009.192.168.207.54.1435167945.squirrel@webmail.etecsa.cu> Date: Wed, 24 Jun 2015 13:02:47 -0500 (GMT+5) Subject: Re: Replication broken. Stale data in slave Database From: "Gilberto Castillo" To: "Alberto Olivares" Cc: gilberto.castillo@etecsa.cu, pgsql-admin@postgresql.org Reply-To: gilberto.castillo@etecsa.cu User-Agent: SquirrelMail/1.4.8-5.el5_4.10 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Status: not scanned, disabled by settings X-KLMS-AntiPhishing: Clean, 2015/06/24 13:52:08 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2015/06/24 07:13:00 #8278661 X-KLMS-AntiVirus-Status: Clean, skipped X-Pg-Spam-Score: -3.3 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org > Hi, > > I thought about creating a cron job but we cannot run it monthly, we need > to do it just in case the replication fails because the master database > breaks. You not use failover? What use for manager the replication? Saludos, Gilberto Castillo ETECSA, La Habana, Cuba -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin