Yes. I'm advocating something "built-in" to Postgres. Any or all of those are likely a great starting point.
As for protobuf, I'm a big advocate -- it is easy to use, fast, extensible, runs on lots of platforms, and produces very compact output. However it introduces a few dependencies to the build and that may make it too difficult for wide options within Postgres. On Mon, Sep 25, 2017 at 10:07 AM, Joshua D. Drake <j...@commandprompt.com> wrote: > 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. ***** >
