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

Kevin Grittner <kevin.grittner@wicourts.gov>

From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>

To: "Andres Freund" <andres@2ndquadrant.com>, <pgsql-hackers@postgresql.org>

Cc: "Simon Riggs" <simon@2ndquadrant.com>, "Robert Haas" <robertmhaas@gmail.com>, "Daniel Farina" <daniel@heroku.com>,"Tom Lane" <tgl@sss.pgh.pa.us>

Date: 2012-06-19T22:27:32Z

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 →

Don't waste the last segment of each 4GB logical log file.
- dfda6ebaec67 9.3.0 cited
Stamp HEAD as 9.3devel.
- bed88fceac04 9.3.0 cited
Wake WALSender to reduce data loss at failover for async commit.
- 2c8a4e9be273 9.2.0 cited
Make the visibility map crash-safe.
- 503c7305a1e3 9.2.0 cited

Andres Freund <andres@2ndquadrant.com> wrote:

> Yes, thats definitely a valid use-case. But that doesn't preclude
> the other - also not uncommon - use-case where you want to have
> different master which all contain up2date data.

I agree.  I was just saying that while one requires an origin_id,
the other doesn't.  And those not doing MM replication definitely
don't need it.

-Kevin