Re: [PATCH] XLogReader v2

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Satoshi Nagayasu <snaga(at)uptime(dot)jp>, pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, satoshi(dot)nagayasu(at)gmail(dot)com
Subject: Re: [PATCH] XLogReader v2
Date: 2012-07-23 14:17:39
Message-ID: CA+TgmoauCrvbymOck_4Lj8_12zTHDHh7Yj09buyuHGkvOjmgtQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 23, 2012 at 3:19 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On Thursday, July 19, 2012 07:18:08 PM Satoshi Nagayasu wrote:
>> I agree with that we need more sophisticated way to share the code
>> between the backend and several utilities (including xlogdump),
>> but AFAIK, a contrib module must allow to be built *without* the core
>> source tree.
> I don't think thats reasonable. The amount of code duplication required to
> support that usecase is just not reasonable. Especially if you want to support
> pre 9.3 and 9.3+.

It seems like the direction this is going is that the xlog reading
stuff should be a library which is used by both the backend and 1 or
more xlog decoding tools.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-07-23 14:23:35 Re: enhanced error fields
Previous Message Robert Haas 2012-07-23 14:12:19 Re: 9.2 release schedule