| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Changeset Extraction v7.6.1 |
| Date: | 2014-02-18 02:49:59 |
| Message-ID: | CAM3SWZRreGfaN0h7nqE81CYHogipvcjpfaxpfTsHGogpPpdj0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 17, 2014 at 6:35 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> What I actually suspect is going to happen if we ship this as-is is
> that people are going to start building logical replication solutions
> on top of the test_decoding module even though it explicitly says that
> it's just test code. This is *really* cool technology and people are
> *hungry* for it. But writing C is hard, so if there's not a polished
> plugin available, I bet people are going to try to use the
> not-polished one. I think we try to get out ahead of that.
Tom made a comparison with FDWs, so I'll make another. The Multicorn
module made FDW authorship much more accessible by wrapping it in a
Python interface, I believe with some success. I don't want to stand
in the way of building a fully-featured test_decoding module, but I
think that those that would misuse test_decoding as it currently
stands can be redirected to a third-party wrapper. As you say, it's
pretty cool stuff, so it seems likely that someone will build one for
us.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2014-02-18 02:50:43 | Rowcounts marked by create_foreignscan_path() |
| Previous Message | Robert Haas | 2014-02-18 02:35:23 | Re: Changeset Extraction v7.6.1 |