From: | Bert <biertie(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
Cc: | "Sofer, Yuval" <Yuval_Sofer(at)bmc(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, "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: | Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help |
Date: | 2013-04-18 16:16:15 |
Message-ID: | CAFCtE1=UdQjXGXqwTOwt5AZbxXjEC55gHw_Uq0nnHzk0Tqcs4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)elevated-dev(dot)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(at)elevated-dev(dot)com
> http://www.elevated-dev.com/
> (303) 722-0567 voice
>
>
>
>
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
--
Bert Desmet
0477/305361
From | Date | Subject | |
---|---|---|---|
Next Message | chanh.tran | 2013-04-19 12:58:23 | Pb migrating database from Postgres 8.1 to 8.4 |
Previous Message | Scott Ribe | 2013-04-18 16:13:27 | Re: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help |