Thread: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help

<div class="WordSection1"><p class="MsoPlainText"><span style="font-size:12.0pt;color:#1F497D">Hi, </span><p
class="MsoPlainText"><spanstyle="font-size:12.0pt;color:#1F497D"> </span><p class="MsoPlainText"><span
style="font-size:12.0pt;color:#1F497D">Iam using Postgres DB with stand by database, configured with streaming in
synchronizedmode (each commit on primary DB waits for commit on secondary DB).</span><p class="MsoPlainText"><span
style="font-size:12.0pt;color:#1F497D"> </span><pclass="MsoPlainText"><span
style="font-size:12.0pt;color:#1F497D">Sometimeswe suffer from network issues and as consequences, secondary machine is
notavailable.</span><p class="MsoPlainText"><span style="font-size:12.0pt;color:#1F497D"> </span><p
class="MsoPlainText"><spanstyle="font-size:12.0pt;color:#1F497D">In these situations, our application is stuck and do
notrespond anymore, since no confirmation comes from the secondary Postgres (obviously… it is down or unavailable….).
</span><pclass="MsoPlainText"><span style="font-size:12.0pt;color:#1F497D"> </span><p class="MsoPlainText"><span
style="font-size:12.0pt;color:#1F497D">Isthere any parameter that I can use, to enable recovering from hanging on until
someoneof us re-establish connection to secondary DB?</span><p class="MsoPlainText"><span
style="font-size:12.0pt;color:#1F497D">Maybesome configuration parameter that sets the time interval for being stuck
becauseof unavailable secondary Postgres? </span><p class="MsoPlainText"><span
style="font-size:12.0pt;color:#1F497D"> </span><pclass="MsoPlainText"><span
style="font-size:12.0pt;color:#1F497D">Pleasehelp, </span><p class="MsoPlainText"><span
style="font-size:12.0pt;color:#1F497D"> </span><pclass="MsoPlainText"><span
style="font-size:12.0pt;color:#1F497D">Thanks,</span><pclass="MsoPlainText"><span
style="font-size:12.0pt;color:#1F497D"> </span><pclass="MsoNormal"> <p class="MsoNormal"><b><span
style="font-family:"ArialNarrow","sans-serif"">Yuval Sofer</span></b><p class="MsoNormal"><b><span
style="font-family:"ArialNarrow","sans-serif"">BMC Software</span></b><p class="MsoNormal"><b><span
style="font-family:"ArialNarrow","sans-serif"">CTM&D Business Unit</span></b><p class="MsoNormal"><b><span
style="font-family:"ArialNarrow","sans-serif"">DBA Team</span></b><p class="MsoNormal"><b><span
style="font-family:"ArialNarrow","sans-serif"">972-52-4286-282</span></b><p class="MsoNormal"><a
href="mailto:yuval_sofer@bmc.com"><b><spanstyle="font-family:"Arial
Narrow","sans-serif";color:blue">yuval_sofer@bmc.com</span></b></a><b><spanstyle="font-family:"Arial
Narrow","sans-serif""></span></b><pclass="MsoNormal"> <p class="MsoNormal"> <p class="MsoNormal" dir="RTL"
style="text-align:right;direction:rtl;unicode-bidi:embed"><spandir="LTR"> </span><p class="MsoNormal"> </div> 

Sofer, Yuval <Yuval_Sofer@bmc.com> wrote:

> 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?

Use asynchronous mode. There is no way for 'only a little bit
synchronized mode'. We are not in the mysql-world ...



Andreas
-- 
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect.                              (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly."   (unknown)
Kaufbach, Saxony, Germany, Europe.              N 51.05082°, E 13.56889°