Horton

Re: [PATCH 13/16] Introduction of pair of logical walreceiver/sender

Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>

View thread
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Andres Freund <andres@2ndquadrant.com>, pgsql-hackers@postgresql.org
Date: 2012-06-29T15:39:09Z
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 29.06.2012 18:28, Kevin Grittner wrote:
> It would be nice if there was at least a thin layer of the sender
> portion which could by used by a stand-alone program.  I can think
> of lots of useful reasons to "T" the WAL stream -- passing through
> the stream with little or no modification to at least one side.  As
> just one example, I would like a program to write traditional WAL
> files to match what an archive on the sending side would look like
> while passing the stream through to an asynchronous hot standby.

That isn't really related to the logical replication stuff, but I agree 
that would be cool. You can sort of do that with cascading replication, 
but a thin stand-alone program would be nicer.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com