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+YEMAzBdP8Cg4yX05u4pjN0WHWZaVjGG_nZ_jG7dHP1n=g@mail.gmail.com
Whole thread Raw
In response to Re: pglogical_output - a general purpose logical decoding output plugin  (Tomasz Rybak <tomasz.rybak@post.pl>)
Responses Re: pglogical_output - a general purpose logical decoding output plugin  (Petr Jelinek <petr@2ndquadrant.com>)
List pgsql-hackers
On 19 November 2015 at 03:42, Tomasz Rybak <tomasz.rybak@post.pl> wrote:

I've just skimmed through the patch.
As you removed 9.4 compatibility - are mentions of 9.4 and 9.5 
compatibility needed in README.md and README.plhooks?

Thanks. Removed.

Here's a v3 patch. Changes since v2:

- fix stray braces in commit json output
- significantly expand pg_regress tests
- quote all json keys
- validate all json in tests
- decode json startup message to a table
- filter out mutable keys in json startup message
- troubleshooting section of README covers using json
- documentation copy editing

Full patch against master attached. Diff since v2 at 


While the downstream client using the binary protocol is still too WIP, the json support is useful for all sorts of apps. It has all the same support for hooks and filtering, origin information, etc. I'd love to hear from anyone who's trying it out.

SGML conversion of docs still WIP.

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

pgsql-hackers by date:

Previous
From: Kouhei Kaigai
Date:
Subject: Re: CustomScan in a larger structure (RE: CustomScan support on readfuncs.c)
Next
From: Peter Geoghegan
Date:
Subject: Minor ON CONFLICT comment tweak