| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Issues with Quorum Commit |
| Date: | 2010-10-13 04:47:31 |
| Message-ID: | AANLkTi=t5ZmYC-fabXQKVxm=BBWGTy2smF9=UnAvghrE@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Oct 9, 2010 at 1:41 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> And, I'd like to know whether the master waits forever because of the
>> standby failure in other solutions such as Oracle DataGuard, MySQL
>> semi-synchronous replication.
>
> MySQL used to be fond of simiply failing sliently. Not sure what 5.4 does,
> or Oracle. In any case MySQL's replication has always really been async
> (except Cluster, which is a very different database), so it's not really a
> comparison.
IIRC, MySQL *semi-synchronous* replication is not async, so it can be
comparison. Of course, though MySQL default replication is async.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2010-10-13 05:21:32 | Re: Issues with Quorum Commit |
| Previous Message | Fujii Masao | 2010-10-13 04:43:57 | Re: Issues with Quorum Commit |