| From: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: How to choose new master from slaves.? |
| Date: | 2022-08-06 20:45:32 |
| Message-ID: | 20220806204532.6zofkznvzgprckfa@hjp.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2022-08-06 15:06:06 -0500, Ron wrote:
> On 8/6/22 03:40, Peter J. Holzer wrote:
> > Using sync replication on an unstable link is probably not a good idea.
> > Every time the link goes down, A freezes. Is this what you want?
>
> I had to fight my end users about how to replicate a SQL Server database
> across a WAN. They of course wanted it synchronously replicated, but I
> insisted that was a horrible idea, for the exact reason you mentioned
> (though it "only" freezes when the untransmitted transmitted transaction
> logs fill of the primary database's disk).
Doesn't synchronous mean that a commit only returns when the transaction
has been replicated?
(The database can work on other transactions in the meantime, but that
client is blocked.)
hp
--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp(at)hjp(dot)at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2022-08-06 21:13:08 | Re: How to choose new master from slaves.? |
| Previous Message | Ron | 2022-08-06 20:06:06 | Re: How to choose new master from slaves.? |