Re: Manage slot in logical/pglogical replication

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: dpat <denni(dot)pat(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Manage slot in logical/pglogical replication
Date: 2017-07-13 15:55:31
Message-ID: 20170713155531.hfzfxdvibw46bn6x@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

dpat wrote:

> i have configure a master-replica replication with new pglogical 2.0.
> I have to replicate data over MPLS/VPN, so there is a possibility that the
> link temporarily interrupts.
> I know that you have to be accurately estimated pg_xlog folder.
> How can I handle the prolonged interruption of the link?
> Can I just extend the folder? Or drop the slot?

Yeah, data accumulates in the origin side ("master"), so you need to
make sure you have sufficient room in pg_xlog to hold all the data
generated during the network interruption.

Dropping the slot would of course release the disk space, but it would
mean that you'd have to re-create the replica afterwards. I suppose you
could have pg_xlog large enough to hold as much data as possible for a
mid-sized network interruption, and drop the slot as a last resource if
a connection interrupts for long enough that you risk causing
reliability problems in the origin.

> I can create a consumer who temporarily saves the data in an external file?

I don't think so.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Edmundo Robles 2017-07-13 15:57:46 I can't cancel/terminate query.
Previous Message Tom Lane 2017-07-13 15:24:10 Re: Systemd support (was:Re: Please say it isn't so)