Re: Replication broken. Stale data in slave Database

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 16:53:11
Message-ID: CAGdoAzjDx+--LWoZD0Wvmw6gWS3G2wQrSCuL-cJO+Z9s+FqHfw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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.

Regards,
Alberto
On 24 Jun 2015 5:46 pm, "Gilberto Castillo" <gilberto(dot)castillo(at)etecsa(dot)cu>
wrote:

>
> > Hi Gilberto,
> >
> > Ups. So, I cannot try to use this solution. Any other ideas?
>
> Use an cron of SO, Monthy. Call an script what delete the old wal.
>
> 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/>*

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alberto Olivares 2015-06-24 17:26:09 Re: Replication broken. Stale data in slave Database
Previous Message Gilberto Castillo 2015-06-24 16:47:56 Re: Replication broken. Stale data in slave Database