pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Gilberto Castillo <gilberto.castillo@etecsa.cu>
To: Alberto Olivares <alberto.olivares@snowflakesoftware.com>
Cc: gilberto.castillo@etecsa.cu
Cc: pgsql-admin@postgresql.org
Subject: Re: Replication broken. Stale data in slave Database
Date: Wed, 24 Jun 2015 13:41:14 -0500 (GMT+5)
Message-ID: <40347.192.168.207.54.1435171274.squirrel@webmail.etecsa.cu> (raw)
In-Reply-To: <CAGdoAzg60bzjQS8=jLqSv03s9hsTapaJ2KdYtOzUE6cD0Maj+g@mail.gmail.com>
References: <CAGdoAzgERUntgCy-gG2wpL+g3T1rEDDSa+G88=W6pAFXscJ2mw@mail.gmail.com>
	<37952.192.168.207.54.1435162036.squirrel@webmail.etecsa.cu>
	<CAGdoAzh+QHVPG1a1Ou+USMHAR-M06y=XGa_5_Y53gr_dzQ6xgw@mail.gmail.com>
	<37964.192.168.207.54.1435162661.squirrel@webmail.etecsa.cu>
	<CAGdoAziW74B9ve7uXMJemqVKJLZaPBYk6zc-9uo2qfsDKOQufA@mail.gmail.com>
	<37991.192.168.207.54.1435164476.squirrel@webmail.etecsa.cu>
	<CAGdoAziFN5ywxxM+uznbt+msh1UL4tW_3m4Wmjhm1YoNMfOH2w@mail.gmail.com>
	<39009.192.168.207.54.1435167945.squirrel@webmail.etecsa.cu>
	<CAGdoAzjDx+--LWoZD0Wvmw6gWS3G2wQrSCuL-cJO+Z9s+FqHfw@mail.gmail.com>
	<39343.192.168.207.54.1435168967.squirrel@webmail.etecsa.cu>
	<CAGdoAzj5YHWtEnyoN6QNJpqwbXS009D0bUbLdiHHiAhryyR02Q@mail.gmail.com>
	<40206.192.168.207.54.1435170972.squirrel@webmail.etecsa.cu>
	<CAGdoAzg60bzjQS8=jLqSv03s9hsTapaJ2KdYtOzUE6cD0Maj+g@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>


> Not sure if I can do that when the master database is shut down

Yes, In fact both server must be turned off for safety.


> On 24 Jun 2015 6:36 pm, "Gilberto Castillo" <gilberto.castillo@etecsa.cu>
> wrote:
>
>> > 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



view thread (16+ messages)  latest in thread

Message-ID: <40347.192.168.207.54.1435171274.squirrel@webmail.etecsa.cu>
Permalink:  ../40347.192.168.207.54.1435171274.squirrel@webmail.etecsa.cu/
Also on:    postgresql.org/message-id/40347.192.168.207.54.1435171274.squirrel@webmail.etecsa.cu

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: gilberto.castillo@etecsa.cu, alberto.olivares@snowflakesoftware.com
  Subject: Re: Replication broken. Stale data in slave Database
  In-Reply-To: <40347.192.168.207.54.1435171274.squirrel@webmail.etecsa.cu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox