Horton
Menu

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

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: Heikki Linnakangas <hlinnakangas@vmware.com>, pgsql-hackers@postgresql.org
Date: 2012-12-11T20:10:32Z
Lists: pgsql-hackers 
On Tue, Dec 11, 2012 at 9:44 AM, Andres Freund <andres@2ndquadrant.com> wrote:
>> * How about we move pg_xlogdump to contrib? It doesn't feel like the kind of
>> essential tool that deserves to be in src/bin.
>
> contrib would be fine, but I think src/bin is better. There have been
> quite some bugs by now where it would have been useful to have a
> reliable xlogdump in core so its really installed.

I think I'm with Heikki on this one.  Dumping xlog data is useful, but
it's really for developers and troubleshooters, not something we
expect people to do on a regular basis, so contrib seems appropriate.

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

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