| From: | Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com> |
|---|---|
| To: | MauMau <maumau307(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [RFC: bug fix?] Connection attempt block forever when the synchronous standby is not running |
| Date: | 2014-07-07 04:20:12 |
| Message-ID: | BF2827DCCE55594C8D7A8F7FFD3AB7713DE14EA0@SZXEML508-MBX.china.huawei.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04 July 2014 19:29, MauMau Wrote:
> [How to fix]
> Of course, adding "-o '-c synchronous_commit=local'" or "-o '-c
> synchronous_standby_names='" to pg_ctl start in the recovery script
> would prevent the problem.
>
> But isn't there anything to fix in PostgreSQL? I think the doc needs
> improvement so that users won't misunderstand that only write
> transactions would block at commit.
As of now there is no solution for this in PostgreSQL but I had submitted a patch "Standalone synchronous master" in
9.4 2014-01 CommitFest, which was rejected because of some issues. This patch was meant to degrade the synchronous
level of master, if all synchronous standbys are down.
I plan to resubmit this with better design sometime in 9.5.
Thanks and Regards,
Kumar Rajeev Rastogi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-07-07 05:14:21 | Re: [RFC: bug fix?] Connection attempt block forever when the synchronous standby is not running |
| Previous Message | Jeff Davis | 2014-07-07 04:11:36 | Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls |