| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Farina <daniel(at)heroku(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |
| Date: | 2012-06-20 08:44:54 |
| Message-ID: | 4FE18D86.7030602@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 20.06.2012 11:34, Simon Riggs wrote:
> On 20 June 2012 16:23, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>
>> It's only needed for multi-master replication, where the same table can be
>> updated from multiple nodes. Just leave that out for now. There's plenty of
>> functionality and issues left even without that.
>
> Huh? Multi-master replication is what is being built here and many
> people want that.
Sure, but presumably you're going to implement master-slave first, and
build multi-master on top of that. What I'm saying is that we can leave
out the origin-id for now, since we don't have agreement on it, and
revisit it after master-slave replication is working.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-06-20 08:55:09 | Re: Too frequent message of pgbench -i? |
| Previous Message | Simon Riggs | 2012-06-20 08:34:54 | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |