| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Nikhil <nikhilsmenon(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: BDR replication |
| Date: | 2016-01-30 14:36:25 |
| Message-ID: | CAMsr+YEW9f1cOFLvPADZZWhP-T+upH-0QvEdLCNBno0YT3sH=w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 29 January 2016 at 18:27, Nikhil <nikhilsmenon(at)gmail(dot)com> wrote:
> Is there any way to specify priority for replication. or any parameter
> which guarantees something about replication (speed at which it replicates,
> number of minimum replicas to write).
>
Not yet. Not in core PostgreSQL streaming replication, nor in BDR or
pglogical etc.
Right now you have "synchronous" or "not synchronous" and at most one
synchronous node.
Does BDR has a configuration for differentiated services in replication.
>
No. It's mesh multimaster and all replicated data is treated equally.
There's no concept of replication priority, nor am I sure how we could
implement such a thing. Data is either replicated or not replicated.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-01-30 16:24:02 | Re: BRIN indexes |
| Previous Message | Augori | 2016-01-30 13:18:50 | Re: Transaction check error installing PostGIS |