Re: How to choose new master from slaves.?

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: How to choose new master from slaves.?
Date: 2022-08-06 21:13:08
Message-ID: e8e2a70c-ec40-f1a8-3c56-5fb0fb190b81@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 8/6/22 15:45, Peter J. Holzer wrote:
> 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?

Correct.  I don't know what I was thinking when I wrote that.

Probably that transaction log data gets queued up and not deleted if it
can't send the data across.

> (The database can work on other transactions in the meantime, but that
> client is blocked.)

Eventually any client doing writes blocks.  Readers might block if a writer
took an exclusive lock,

--
Angular momentum makes the world go 'round.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Frank Millman 2022-08-07 05:30:00 Question about locking
Previous Message Peter J. Holzer 2022-08-06 20:45:32 Re: How to choose new master from slaves.?