| 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:01:36 |
| Message-ID: | CAGdoAziFN5ywxxM+uznbt+msh1UL4tW_3m4Wmjhm1YoNMfOH2w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi Gilberto,
Ups. So, I cannot try to use this solution. Any other ideas?
Thanks.
Regards,
Alberto.
*Alberto Olivares Colas*Technical Consultant
Snowflake Software
Tel.: +44 (0)2380 386578
Email: alberto(dot)olivares(at)snowflakesoftware(dot)com
Website: www.snowflakesoftware.com
Twitter: @sflakesoftware <http://www,twitter(dot)com(at)sflakesoftware/>
Follow us on LinkedIn <http://www.linkedin.com/company/snowflake-software>
*Winner of IHS Jane's ATC Award - Enabling Technology*
*Read more <http://www.snowflakesoftware.com/2015/03/janes-award/>*
Registered in England & Wales. Registered Number: 4294244
-----------------------------------------------------------------------------------------
On 24 June 2015 at 17:47, Gilberto Castillo <gilberto(dot)castillo(at)etecsa(dot)cu>
wrote:
>
> > Hi Gilberto,
> >
> > Thanks for your answer.
> >
> > Do you know how to configure the pg_archivecleanup just in the event the
> > primary database goes down?
>
>
> Look pg_archivecleanup is configured in the slave in version major pg 9.4
>
> It's not your case.
>
>
> 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 | Gilberto Castillo | 2015-06-24 16:07:16 | Re: Replication broken. Stale data in slave Database |
| Previous Message | Alberto Olivares | 2015-06-24 15:40:24 | Re: Replication broken. Stale data in slave Database |