From: | Alberto Olivares <alberto(dot)olivares(at)snowflakesoftware(dot)com> |
---|---|
To: | gilberto(dot)castillo(at)etecsa(dot)cu |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Replication broken. Stale data in slave Database |
Date: | 2015-06-24 17:26:09 |
Message-ID: | CAGdoAzj5YHWtEnyoN6QNJpqwbXS009D0bUbLdiHHiAhryyR02Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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.
On 24 Jun 2015 6:03 pm, "Gilberto Castillo" <gilberto(dot)castillo(at)etecsa(dot)cu>
wrote:
>
> > 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
>
>
--
*Winner of IHS Jane's ATC Award - Enabling Technology*
*Read more <http://www.snowflakesoftware.com/2015/03/janes-award/>*
From | Date | Subject | |
---|---|---|---|
Next Message | Alberto Olivares | 2015-06-24 17:38:30 | Re: Replication broken. Stale data in slave Database |
Previous Message | Alberto Olivares | 2015-06-24 16:53:11 | Re: Replication broken. Stale data in slave Database |