| From: | Dave Cramer <davecramer(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Binary support for pgoutput plugin |
| Date: | 2019-06-09 00:40:43 |
| Message-ID: | CADK3HHJ4tsFDNNZ=YyDAEuhzVoUCCXAK0GOAvvNYkZMi-Rw3CA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 8 Jun 2019 at 20:09, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2019-06-08 19:41:34 -0400, Dave Cramer wrote:
> > So the reason we are discussing using pgoutput plugin is because it is
> part
> > of core and guaranteed to be in cloud providers solutions.
>
> IMO people needing this should then band together and write one that's
> suitable, rather than trying to coerce test_decoding and now pgoutput
> into something they're not made for.
>
At the moment it would look a lot like pgoutput. For now I'm fine with no
changes to pgoutput other than binary
Once we have some real use cases we can look at writing a new one. I would
imagine we would actually start with
pgoutput and just add to it.
Thanks,
Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2019-06-09 01:15:09 | Re: Should we warn against using too many partitions? |
| Previous Message | Andres Freund | 2019-06-09 00:09:44 | Re: Binary support for pgoutput plugin |