Re: [HACKERS] Built-in plugin for logical decoding output

2017-09-25 Thread Gregory Brail
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 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 >>

Re: [HACKERS] Built-in plugin for logical decoding output

2017-09-25 Thread Gregory Brail
I'm encouraged that pgoutput exists and I'm sorry that I missed it before. I think it's fine as a binary-only format. If someone can write a client for the Postgres wire protocol as documented in Chapter 52 of the docs, then they should have no trouble consuming the output from pgoutput. However,

Re: [HACKERS] Built-in plugin for logical decoding output

2017-09-22 Thread Gregory Brail
uire a more detailed explanation which I'm happy to put together.) On Fri, Sep 22, 2017 at 4:01 PM, Alvaro Hernandez wrote: > > > On 23/09/17 00:28, Gregory Brail wrote: > >> We have been working on a project that makes extensive use of logical >> replication for use in

[HACKERS] Built-in plugin for logical decoding output

2017-09-22 Thread Gregory Brail
We have been working on a project that makes extensive use of logical replication for use inside Apigee (which is a very small part of Google): https://github.com/apigee-labs/transicator In order to do this, we had to write our own logical replication plugin because the supplied "test_decoding" p