Re: Why PostgreSQL doesn't implement a semi sync replication? - Mailing list pgsql-hackers

From Francisco Olarte
Subject Re: Why PostgreSQL doesn't implement a semi sync replication?
Date
Msg-id CA+bJJbxDjajKfAinvjB=ujxR0HJKber1nHdPxLCsF=-6oo-SMA@mail.gmail.com
Whole thread Raw
In response to Why PostgreSQL doesn't implement a semi sync replication?  (余森彬 <justdoit920823@gmail.com>)
Responses Re: Why PostgreSQL doesn't implement a semi sync replication?  (Petr Jelinek <petr@2ndquadrant.com>)
List pgsql-hackers
On Fri, Nov 11, 2016 at 4:40 AM, 余森彬 <justdoit920823@gmail.com> wrote:
>     As we know, the synchronous commit process is blocked while receives
> from acknowledgement from standby in
> PostgreSQL.This is good for data consistence in master and standby, and
> application can get important data from standby.But
> when the standby crash or network goes wrong, the master could be hang.Is
> there a feature plan for a semi sync like MySQL
> InnoDB(set a timer, and become asynchronous when timeout)?

JMO, but it seems this basically means any process should be dessigned
to cope with the posibility of not having replicated data after
commit, so, why bother with synchronous replication in the first
place?

Francisco Olarte.



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Improving RLS planning
Next
From: Tom Lane
Date:
Subject: Re: Do we need use more meaningful variables to replace 0 in catalog head files?