| From: | Bhupendra Kumar <bhupendra(dot)kumar(at)indiamart(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Facing issue with Global lock in postgres-bdr |
| Date: | 2016-09-15 06:22:01 |
| Message-ID: | CAAHK9Ynr869d0T2xvZ7t+qAtQ+SoD1vm-YpW6MC3Adp=RE2n5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
We have setup postgres-bdr, in that I am facing global lock situation in
one of node due to this replication between 2 nodes has been stopped and I
am not table to perform any DDL activity in my bdr cluster.
I have used below solution but unfortunately it is not working. Please
help me to get rid of this issue.
ALTER DATABASE dbname SET bdr.permit_ddl_locking = false;
Regards,
Bhupendra Kumar
--
*Watch our latest TV Commercial #IndiaKiKhoj
<https://youtu.be/SoBcg2z0pZE%20%20>*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Papst | 2016-09-15 06:28:02 | Re: BUG #14320: systemd terminates postgresql hot standby instance 90 seconds after start |
| Previous Message | Peter Eisentraut | 2016-09-15 00:19:32 | Re: BUG #14320: systemd terminates postgresql hot standby instance 90 seconds after start |