Обсуждение: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help
Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help
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
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 connectionto 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 asynchronousreplication. -- Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice
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. :)
Bert
On Apr 18, 2013, at 9:40 AM, Sofer, Yuval wrote:No, that's what synchronous means. What you're describing is asynchronous, and it seems like you should consider using asynchronous replication.
> 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?
--
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