| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Gregory Brail <gregbrail(at)google(dot)com>, Alvaro Hernandez <aht(at)ongres(dot)com> |
| Cc: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Built-in plugin for logical decoding output |
| Date: | 2017-09-25 17:07:48 |
| Message-ID: | 8b033e44-d957-870f-8d7a-e5773ac690bc@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/25/2017 09:59 AM, Gregory Brail wrote:
> However, I can't find any docs for the output format of pgoutput, which
> is going to make it less likely for people to be able to consume it. Is
> anyone working on docs? I know that it's a painful process.
>
> I also think that a JSON-format (or configurable format) plugin would
> make this part of PG much more usable and I'd encourage the community to
> come up with one.
https://github.com/ildus/decoder_json
https://github.com/posix4e/jsoncdc
https://github.com/leptonix/decoding-json
https://github.com/Aloomaio/psql-json-decoder
Thanks,
JD
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.us
***** Unless otherwise stated, opinions are my own. *****
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Hernandez | 2017-09-25 17:13:05 | Re: Built-in plugin for logical decoding output |
| Previous Message | Gregory Brail | 2017-09-25 16:59:40 | Re: Built-in plugin for logical decoding output |