From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Cj B <blackc2004(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: bdr appears to be trying to replicate to itself |
Date: | 2015-11-17 01:23:31 |
Message-ID: | CAMsr+YFKCwUAoU6OJ1pqozeroBVXCRO65Efhd=57Vhf_TWwPzA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 17 November 2015 at 00:33, Cj B <blackc2004(at)gmail(dot)com> 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 autovacuum to clean
up dead tuples in the catalogs.
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
oversight in those checks. If you're able to reproduce this state I'd like
to hear details on how.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Uckun | 2015-11-17 01:47:10 | Re: Importing directly from BCP files |
Previous Message | Adrian Klaver | 2015-11-17 00:52:17 | Re: Importing directly from BCP files |