On 8/4/22 02:43, Sacheen Birhade wrote:
@font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0;}@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;}span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri",sans-serif; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",sans-serif;}div.WordSection1 {page:WordSection1;}Hi All,
I have a very basic question about streaming replication feature of Postgres.
Let’s assume I have servers A, B, C, D, & E with postgres installed with streaming replication as follow:
A à B ( sync replication )
A à C ( async replication )
A à D ( async replication )
A à E ( async replication )
A is master & rest are slaves.
Now my question is:
Assume replication link between A & B may/may not stable. If A goes down, how will I choose my new master from slaves? What are criteria to choose new master?
By "link between A & B may/may not stable", do you mean that B might not actually be synchronized?
--
Angular momentum makes the world go 'round.
