Re: hot standby PSQL 9.1 Windows 2008 Servers

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <chinnaobi(at)gmail(dot)com>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: hot standby PSQL 9.1 Windows 2008 Servers
Date: 2012-05-31 16:24:10
Message-ID: 4FC754DA0200002500047F12@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

chinnaobi wrote:

> You mean when the primary which is going to switch its role to
> standby might not have sent all the WAL records to the standby and
> If it is switched to standby it has more WAL records than the
> standby which is now serves as primary. Is it ??

What happens when there is a network fault between the primary and
the standby, but not between the primary and some of the clients
updating it? Similarly, if this is asynchronous replication, what if
there have been commits on the primary which were still in the
network buffer when the primary crashed?

Clean automated failover is not a trivial task. If you are writing
your own, it would be best to follow the steps recommended in the
documentation rather closely.

-Kevin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergey Koposov 2012-05-31 16:54:54 Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile
Previous Message Merlin Moncure 2012-05-31 16:18:10 Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile