Hi Alvaro, I could not determine what exactly the command was. But I "fixed" it by using bdr.skip_changes_upto() to skip this change from application. The replication resumed after that. Best Regards, Daniel -----Original Message----- From: Alvaro Aguayo Garcia-Rada [mailto:aaguayo@xxxxxxxxxxxxxxx] Sent: Monday, February 11, 2019 2:21 PM To: Daniel Fink (PDF) Cc: pgsql-general Subject: Re: bdr replication breaks down What's the command you are running to trigger such behaviour? Regards, Alvaro Aguayo Jefe de Operaciones Open Comb Systems E.I.R.L. (+51-1) 337-7813 Anexo 4002 www.ocs.pe ----- Original Message ----- From: "Daniel Fink (PDF)" <daniel.fink@xxxxxxx> To: "pgsql-general" <pgsql-general@xxxxxxxxxxxxxxxxxxxx> Sent: Monday, 11 February, 2019 05:18:30 Subject: bdr replication breaks down Hi all, I have a bdr replication setup that worked fine until recently. But it seems like one command cannot be replicated, and it breaks down the whole process on all hosts where it is sent to. I appended part of the log file, it gets repeated over and over. Can I somehow omit this command and try if the next one works? Best Regards, Daniel Fink < 2019-02-08 00:00:01.658 CET >ERROR: schema "pg_temp_30" does not exist < 2019-02-08 00:00:01.658 CET >CONTEXT: apply QUEUED_DROP in commit 7D/2E3143B0, xid 106791715 commited at 2019-01-28 10:12:34.348577+01 (action #2) from node (6208877715678412212,1,2942745) < 2019-02-08 00:00:01.661 CET >LOG: worker process: bdr (6449651545875285115,1,16388,)->bdr (6208877715678412212,1, (PID 27640) exited with exit code 1 < 2019-02-08 00:00:06.666 CET >LOG: starting background worker process "bdr (6449651545875285115,1,16388,)->bdr (6208877715678412212,1," < 2019-02-08 00:00:07.641 CET >ERROR: schema "pg_temp_30" does not exist < 2019-02-08 00:00:07.641 CET >CONTEXT: apply QUEUED_DROP in commit 7D/2E3143B0, xid 106791715 commited at 2019-01-28 10:12:34.348577+01 (action #2) from node (6208877715678412212,1,2942745) < 2019-02-08 00:00:07.644 CET >LOG: worker process: bdr (6449651545875285115,1,16388,)->bdr (6208877715678412212,1, (PID 27645) exited with exit code 1 < 2019-02-08 00:00:12.649 CET >LOG: starting background worker process "bdr (6449651545875285115,1,16388,)->bdr (6208877715678412212,1," < 2019-02-08 00:00:13.633 CET >ERROR: schema "pg_temp_30" does not exist < 2019-02-08 00:00:13.633 CET >CONTEXT: apply QUEUED_DROP in commit 7D/2E3143B0, xid 106791715 commited at 2019-01-28 10:12:34.348577+01 (action #2) from node (6208877715678412212,1,2942745) *DANIEL FINK* *Senior Software Engineer* *tel* (+49) 89.767062.20 *fax*(+49) 89.767062.11 email daniel.fink@xxxxxxx *PDF Solutions GmbH* * (**a PDF Solutions Company)* Managing Director: Kimon Michaels Schwanthalerstr. 10 D-80336 München, Germany München HRB 87307 DE 128214899 *www.pdf.com <http://www.pdf.com/>* -- This message may contain confidential and privileged information. If it has been sent to you in error, please reply to advise the sender of the error and then immediately permanently delete it and all attachments to it from your systems. If you are not the intended recipient, do not read, copy, disclose or otherwise use this message or any attachments to it. The sender disclaims any liability for such unauthorized use. PLEASE NOTE that all incoming e-mails sent to PDF e-mail accounts will be archived and may be scanned by us and/or by external service providers to detect and prevent threats to our systems, investigate illegal or inappropriate behavior, and/or eliminate unsolicited promotional e-mails (“spam”). If you have any concerns about this process, please contact us at legal.department@xxxxxxx <mailto:legal.department@xxxxxxx>. -- This message may contain confidential and privileged information. If it has been sent to you in error, please reply to advise the sender of the error and then immediately permanently delete it and all attachments to it from your systems. If you are not the intended recipient, do not read, copy, disclose or otherwise use this message or any attachments to it. The sender disclaims any liability for such unauthorized use. PLEASE NOTE that all incoming e-mails sent to PDF e-mail accounts will be archived and may be scanned by us and/or by external service providers to detect and prevent threats to our systems, investigate illegal or inappropriate behavior, and/or eliminate unsolicited promotional e-mails (“spam”). If you have any concerns about this process, please contact us at legal.department@xxxxxxx <mailto:legal.department@xxxxxxx>.
