| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Azimuddin Mohammed <azimeiu(at)gmail(dot)com> |
| Cc: | 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:21:43 |
| Message-ID: | 20180126012143.GB2416@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Greetings,
On our mailing lists, we prefer that replies be in-line and ask that
users not top-post. Please see my response, in-line, below.
* Azimuddin Mohammed (azimeiu(at)gmail(dot)com) wrote:
> So untill my slave comes up master does not commit any transaction which
> means technically my db is non operative?
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
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-01-26 01:37:38 | Re: Sync replication |
| Previous Message | Rakesh Kumar | 2018-01-26 01:09:57 | Re: Sync replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-01-26 01:34:10 | Re: [PATCH] Logical decoding of TRUNCATE |
| Previous Message | Rakesh Kumar | 2018-01-26 01:09:57 | Re: Sync replication |