| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Synchronization levels in SR |
| Date: | 2010-05-27 13:09:12 |
| Message-ID: | AANLkTinL5dKBuVosD35QktA_0ylmxsZUGQxDjXe62mR5@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 27, 2010 at 9:48 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> There could still be additional transactions that the original master
> has committed locally but were not acked to the client. I guess you'd
> just work around that by taking a new base backup from the new master.
Right.
Unfortunately the transaction aborted for a client might have already
been committed in the standby. In this case, we might need to eliminate
the mismatch of transaction status between a client and new master
after failover.
BTW, the similar situation might happen even when only one server is
running. If the server goes down before returning a "success" to a
client after flushing the commit record, the mismatch would happen
after restart of the server.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sander, Ingo (NSN - DE/Munich) | 2010-05-27 13:13:21 | Streaming Replication: Checkpoint_segment and wal_keep_segments on standby |
| Previous Message | Simon Riggs | 2010-05-27 13:08:14 | Straightforward Synchronous Replication |