| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com>, swaxolez <willem(at)pcfish(dot)ca> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: BDR Selective Replication |
| Date: | 2015-04-27 21:38:08 |
| Message-ID: | 553EAC40.6090300@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4/26/15 7:49 AM, Craig Ringer wrote:
> There are also some improvements needed to the user interface - in
> particular, providing a function interface for changing replication set
> memberships for connections so there's no need to manually restart the
> apply backends after a change, and providing default replication sets
> for a node.
If 'default replication set' is the idea of "here's what tables *should*
be getting replicated regardless of whether that's happening or not",
it'd be great if that was done so it could be split out on it's own at
some point. It's a problem that affects all replication systems.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2015-04-28 00:54:53 | Re: BDR Selective Replication |
| Previous Message | Jim Nasby | 2015-04-27 21:34:02 | Re: Invalid memory alloc |