Skip site navigation (1) Skip section navigation (2)

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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [PATCH 02/14] Add support for a generic wal reading facility dubbed XLogReader
Date: 2012-12-11 20:10:32
Message-ID: CA+Tgmob+gjZ6snKK+XM-Fgj6g2kngxGQWiFA8L2_6hiVOF-=Ww@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Dec 11, 2012 at 9:44 AM, Andres Freund <andres(at)2ndquadrant(dot)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


In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2012-12-11 20:12:37
Subject: Re: pg_upgrade problem with invalid indexes
Previous:From: Robert HaasDate: 2012-12-11 20:07:29
Subject: Re: Multiple --table options for other commands

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group