Re: pglogical_output - a general purpose logical decoding output plugin - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: pglogical_output - a general purpose logical decoding output plugin
Date
Msg-id CAMsr+YHAWZwEOwtXZYHfgdX5G66jg4e+s+o7RP52Zpja-ydpxw@mail.gmail.com
Whole thread Raw
In response to Re: pglogical_output - a general purpose logical decoding output plugin  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: pglogical_output - a general purpose logical decoding output plugin
Re: pglogical_output - a general purpose logical decoding output plugin
List pgsql-hackers
On 22 December 2015 at 15:17, Michael Paquier <michael.paquier@gmail.com> wrote:
On Mon, Dec 7, 2015 at 12:10 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
> Removed, change pushed.
>
> Also pushed a change to expose the decoded row data to row filter hooks.
>
> I won't cut a v4 for this, as I'm working on merging the SGML-ified docs and
> will do a v4 with that and the above readme change once that's done.

Patch is moved to next CF, you seem to be still working on it.

Thanks.

Other than SGML-ified docs it's ready. The docs are a hard pre-req of course. In any case most people appear to be waiting for the downstream before looking at it at all, so bumping it makes sense.

I'm a touch frustrated by that, as a large part of the point of submitting the output plugin separately and in advance of the downstream was to get attention for it separately, as its own entity. A lot of effort has been put into making this usable for more than just a data source for pglogical's replication tools. In retrospect naming it pglogical_output was probably unwise.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: custom function for converting human readable sizes to bytes
Next
From: Uriy Zhuravlev
Date:
Subject: Re: Some questions about the array.