On 17 November 2015 at 00:33, Cj B <blackc2...@gmail.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
