Horton

Re: [PATCH 08/16] Introduce the ApplyCache module which can reassemble transactions from a stream of interspersed changes

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: Steve Singer <steve@ssinger.info>, pgsql-hackers@postgresql.org
Date: 2012-06-28T16:01:10Z
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 Tue, Jun 26, 2012 at 8:13 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> It even can be significantly higher than max_connections because
> subtransactions are only recognizable as part of their parent transaction
> uppon commit.

I've been wondering whether sub-XID assignment was going to end up on
the list of things that need to be WAL-logged to enable logical
replication.  It would be nicer to avoid that if we can, but I have a
feeling that we may not be able to.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company