Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z7obR-0004mN-Fg for pgsql-admin@arkaria.postgresql.org; Wed, 24 Jun 2015 17:36:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1Z7obQ-0000Y9-6e for pgsql-admin@arkaria.postgresql.org; Wed, 24 Jun 2015 17:36:48 +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) (envelope-from ) id 1Z7obH-0000MQ-Sh for pgsql-admin@postgresql.org; Wed, 24 Jun 2015 17:36:40 +0000 Received: from imx6.etecsa.cu ([200.55.152.141]) by makus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1Z7obE-00069v-Lm for pgsql-admin@postgresql.org; Wed, 24 Jun 2015 17:36:38 +0000 Received: from mn1.etecsa.cu (unknown [192.168.91.41]) by imx6.etecsa.cu (Postfix) with ESMTP id 6E1AAD6 for ; Wed, 24 Jun 2015 13:35:10 -0400 (CDT) Received: (qmail 11447 invoked by uid 11187); 24 Jun 2015 18:36:12 -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.019358 secs); 24 Jun 2015 18:36:12 -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:36:12 -0000 Received: from 192.168.207.54 (SquirrelMail authenticated user gilberto.castillo) by webmail.etecsa.cu with HTTP; Wed, 24 Jun 2015 13:36:12 -0500 (GMT+5) Message-ID: <40206.192.168.207.54.1435170972.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> <39343.192.168.207.54.1435168967.squirrel@webmail.etecsa.cu> Date: Wed, 24 Jun 2015 13:36:12 -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, > > Yes we have failover. If after a few minutes the master database goes up > the replication works again which is fine. > > But I need something that deletes all records in the slave database > meanwhile master database is down. The reason is because we are sending > not > updated data when this happens and we prefer deleted what it is in the > slave database. Uhmmmm, use rsync of the folder wal in the master and slave. 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