| From: | "Sofer, Yuval" <Yuval_Sofer(at)bmc(dot)com> |
|---|---|
| To: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Cc: | "Zucker, Yehudit" <Yehudit_Zucker(at)bmc(dot)com>, "Abraham, Danny" <danny_abraham(at)bmc(dot)com>, "Miller, Moshe" <Moshe_Miller(at)bmc(dot)com> |
| Subject: | Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help |
| Date: | 2013-04-18 15:39:16 |
| Message-ID: | 2C0926ABD16BB641A8E2F11A549200423DDBC79BED@PHXCCRPRD01.adprod.bmc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
I am using Postgres DB with stand by database, configured with streaming in synchronized mode (each commit on primary DB waits for commit on secondary DB).
Sometimes we suffer from network issues and as consequences, secondary machine is not available.
In these situations, our application is stuck and do not respond anymore, since no confirmation comes from the secondary Postgres (obviously... it is down or unavailable....).
Is there any parameter that I can use, to enable recovering from hanging on until someone of us re-establish connection to secondary DB?
Maybe some configuration parameter that sets the time interval for being stuck because of unavailable secondary Postgres?
Please help,
Thanks,
Yuval Sofer
BMC Software
CTM&D Business Unit
DBA Team
972-52-4286-282
yuval_sofer(at)bmc(dot)com<mailto:yuval_sofer(at)bmc(dot)com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alfonso Afonso | 2013-04-18 17:18:33 | Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help |
| Previous Message | Atri Sharma | 2013-04-18 14:38:49 | Re: Emulating trigger BEFORE SELECT behavior |