Horton
Menu

Re: [PATCH 02/14] Add support for a generic wal reading facility dubbed XLogReader

Heikki Linnakangas <hlinnakangas@vmware.com>

View thread
From: Heikki Linnakangas <hlinnakangas@vmware.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Date: 2012-11-15T14:22:56Z
Lists: pgsql-hackers 
On 15.11.2012 03:17, Andres Freund wrote:
>
> Features:
> - streaming reading/writing
> - filtering
> - reassembly of records
>
> Reusing the ReadRecord infrastructure in situations where the code that wants
> to do so is not tightly integrated into xlog.c is rather hard and would require
> changes to rather integral parts of the recovery code which doesn't seem to be
> a good idea.
>
> Missing:
> - "compressing" the stream when removing uninteresting records
> - writing out correct CRCs
> - separating reader/writer

I'm disappointed to see that there has been no progress on this patch 
since last commitfest. I thought we agreed on the approach I championed 
for here: 
http://archives.postgresql.org/pgsql-hackers/2012-09/msg00636.php. There 
wasn't much work left to finish that, I believe.

Are you going to continue working on this?

- Heikki

Commits

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

  1. Background worker processes

  2. Rearrange storage of data in xl_running_xacts.

  3. Basic binary heap implementation.

  4. Embedded list interface

  5. Refactor xlog.c to create src/backend/postmaster/startup.c