pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedPrimary DB stuck becuase of unavailable standby (synchronized streaming) - please help
2+ messages / 2 participants
[nested] [flat]
* Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help
@ 2013-04-18 15:41 Sofer, Yuval <Yuval_Sofer@bmc.com>
0 siblings, 1 reply; 2+ messages in thread
From: Sofer, Yuval @ 2013-04-18 15:41 UTC (permalink / raw)
To: pgsql-sql; +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] 2+ messages in thread
* Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help
@ 2013-04-18 16:38 Andreas Kretschmer <akretschmer@spamfence.net>
parent: Sofer, Yuval <Yuval_Sofer@bmc.com>
0 siblings, 0 replies; 2+ messages in thread
From: Andreas Kretschmer @ 2013-04-18 16:38 UTC (permalink / raw)
To: pgsql-sql
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°
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2013-04-18 16:38 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-04-18 15:41 Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help Sofer, Yuval <Yuval_Sofer@bmc.com>
2013-04-18 16:38 ` Andreas Kretschmer <akretschmer@spamfence.net>
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