From: | Cj B <blackc2004(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: bdr appears to be trying to replicate to itself |
Date: | 2015-11-16 16:33:34 |
Message-ID: | 2F4DC8FE-E749-4B07-BBBA-EB3B5C4ACA96@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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_6188730679935789649_1_16385__’)
What impact will this have?
Thanks
Cj B
> On Nov 16, 2015, at 8:31 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>
> 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 Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-11-16 16:57:38 | Re: update inside function does not use the index |
Previous Message | Alvaro Herrera | 2015-11-16 16:31:35 | Re: bdr appears to be trying to replicate to itself |