| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Azimuddin Mohammed <azimeiu(at)gmail(dot)com>, Rakesh Kumar <rakeshkumar464(at)aol(dot)com>, pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Sync replication |
| Date: | 2018-01-26 01:37:38 |
| Message-ID: | 20180126013738.GG17847@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Thu, Jan 25, 2018 at 08:21:43PM -0500, Stephen Frost wrote:
> That's correct, which is why it's encouraged to have multiple replicas
> configured when using synchronous replication. In v10, it's possible to
> specify how many synchronous replicas are required to have acknowledged
> a given transaction before a COMMIT is returned to the applicaiton.
> Please review the documentation here:
>
> https://www.postgresql.org/docs/current/static/warm-standby.html#SYNCHRONOUS-REPLICATION
Be careful about the performance impact if there is network latency
between a primary and its standbys. One small correction to what Stephen
says here. It is possible to define multiple synchronous standbys in
v9.6. v10 has added the possibility to define quorum groups. Note that
the grammar as been kept backward-compatible across versions.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-01-26 01:46:48 | Re: Sync replication |
| Previous Message | Stephen Frost | 2018-01-26 01:21:43 | Re: Sync replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-01-26 01:40:27 | Re: [PATCH] Logical decoding of TRUNCATE |
| Previous Message | Petr Jelinek | 2018-01-26 01:36:42 | Re: [PATCH] Logical decoding of TRUNCATE |