From: | Cj B <blackc2004(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | "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 02:06:10 |
Message-ID: | D4B661EF-DD55-477C-BA5B-7E00D880878F@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 <mailto:blackc2004(at)gmail(dot)com>> 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 oversight in those checks. If you're able to reproduce this state I'd like to hear details on how.
Thanks for the help that seems to have done it. I’m not sure how it got into this state either. I do have the commands still that I ran but I doubt that’ll help much. What’s strange is that everything was working fine since May then on Oct 29th it appears to have started keeping copies of the pg_xlog, so something must have happened, but sadly I don’t know what.
I’ll keep an eye on it to see if it happens again.
From | Date | Subject | |
---|---|---|---|
Next Message | M Tarkeshwar Rao | 2015-11-17 02:59:09 | postgreSQL.conf has become zero byte file |
Previous Message | Tim Uckun | 2015-11-17 01:47:10 | Re: Importing directly from BCP files |