Horton

Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node

Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>

View thread
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>, Andres Freund <andres@2ndquadrant.com>, pgsql-hackers@postgresql.org, Robert Haas <robertmhaas@gmail.com>, Daniel Farina <daniel@heroku.com>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2012-06-20T08:44:54Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Don't waste the last segment of each 4GB logical log file.

  2. Stamp HEAD as 9.3devel.

  3. Wake WALSender to reduce data loss at failover for async commit.

  4. Make the visibility map crash-safe.

On 20.06.2012 11:34, Simon Riggs wrote:
> On 20 June 2012 16:23, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.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