pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPrimary DB stuck becuase of unavailable standby (synchronized streaming) - please help
3+ messages / 3 participants
[nested] [flat]
* Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help
@ 2013-04-18 15:40 Sofer, Yuval <Yuval_Sofer@bmc.com>
2013-04-18 16:13 ` Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Scott Ribe <scott_ribe@elevated-dev.com>
0 siblings, 1 reply; 3+ messages in thread
From: Sofer, Yuval @ 2013-04-18 15:40 UTC (permalink / raw)
To: pgsql-admin; +Cc: Zucker, Yehudit <Yehudit_Zucker@bmc.com>; Abraham, Danny <danny_abraham@bmc.com>; Miller, Moshe <Moshe_Miller@bmc.com>
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@bmc.com<mailto:yuval_sofer@bmc.com>
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help
2013-04-18 15:40 Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Sofer, Yuval <Yuval_Sofer@bmc.com>
@ 2013-04-18 16:13 ` Scott Ribe <scott_ribe@elevated-dev.com>
2013-04-18 16:16 ` Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Bert <biertie@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Scott Ribe @ 2013-04-18 16:13 UTC (permalink / raw)
To: Sofer, Yuval <Yuval_Sofer@bmc.com>; +Cc: pgsql-admin@postgresql.org, "Zucker, Yehudit" <Yehudit_Zucker@bmc.com>; Abraham, Danny <danny_abraham@bmc.com>; Miller, Moshe <Moshe_Miller@bmc.com>
On Apr 18, 2013, at 9:40 AM, Sofer, Yuval wrote:
> 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?
No, that's what synchronous means. What you're describing is asynchronous, and it seems like you should consider using asynchronous replication.
--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help
2013-04-18 15:40 Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Sofer, Yuval <Yuval_Sofer@bmc.com>
2013-04-18 16:13 ` Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Scott Ribe <scott_ribe@elevated-dev.com>
@ 2013-04-18 16:16 ` Bert <biertie@gmail.com>
0 siblings, 0 replies; 3+ messages in thread
From: Bert @ 2013-04-18 16:16 UTC (permalink / raw)
To: Scott Ribe <scott_ribe@elevated-dev.com>; +Cc: Sofer, Yuval <Yuval_Sofer@bmc.com>; pgsql-admin; Zucker, Yehudit <Yehudit_Zucker@bmc.com>; Abraham, Danny <danny_abraham@bmc.com>; Miller, Moshe <Moshe_Miller@bmc.com>
Hell**o Yuval,
I would suggest to buy a third server if you want to do synchronous
replication.
However, if your network is broken, I would first fix the network. :)
cheers,
Bert
On Thu, Apr 18, 2013 at 6:13 PM, Scott Ribe <scott_ribe@elevated-dev.com>wrote:
> On Apr 18, 2013, at 9:40 AM, Sofer, Yuval wrote:
>
> > 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?
>
> No, that's what synchronous means. What you're describing is asynchronous,
> and it seems like you should consider using asynchronous replication.
>
> --
> Scott Ribe
> scott_ribe@elevated-dev.com
> http://www.elevated-dev.com/
> (303) 722-0567 voice
>
>
>
>
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
--
Bert Desmet
0477/305361
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2013-04-18 16:16 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-04-18 15:40 Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Sofer, Yuval <Yuval_Sofer@bmc.com>
2013-04-18 16:13 ` Scott Ribe <scott_ribe@elevated-dev.com>
2013-04-18 16:16 ` Bert <biertie@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox