Re: [GENERAL] bdr appears to be trying to replicate to itself

> On 17 November 2015 at 00:33, Cj B > wrote: > > This doesn't explain how the system got into this state. For that it'd really > be necessary to see the steps taken during setup. BDR tries to protect > against attempts to replicate-from-self. Presumably there's an

Re: [GENERAL] bdr appears to be trying to replicate to itself

On 17 November 2015 at 00:33, Cj B wrote: > select pg_drop_replication_slot(‘bdr_16385_6188730679935789649_1_16385__’) > Correct. > What impact will this have? If the slot is unused, it'll allow the WAL that's being held by the slot to be removed. It'll also unpin the catalog xmin to allow

Re: [GENERAL] bdr appears to be trying to replicate to itself

Hi, Yes, I posted on github because I wasn’t sure where to post. And the reason I’m posting here is because I’m not clear about the answer "Drop the slot bdr_16385_6188730679935789649_1_16385__ on the first host.” Do this just mean to select pg_drop_replication_slot(‘bdr_16385_6188730679935789

Re: [GENERAL] bdr appears to be trying to replicate to itself

Cj B wrote: > I noticed a very strange issue starting about 20 days ago and my pg_xlog has > just been filling up since then. For reference, this was also asked on github, and answered there. See https://github.com/2ndQuadrant/bdr/issues/143 -- Álvaro Herrerahttp://www.2ndQuadr