On Fri, May  5, 2017 at 02:28:50PM +0200, Petr Jelinek wrote:
> On 05/05/17 02:46, Bruce Momjian wrote:
> > I am getting tired of saying this.  When I am writing the release notes,
> > I am trying to figure out how it affects our shipped code, and the only
> > "decoding" I know of is test_decoding.  My message was this:
> I actually think the main misunderstanding here comes from the
> test_decoding name interpretation. The test_decoding does not decode
> anything and there are no external "decoders". The decoding happens in
> core, the decoding just provides C API for plugins to consume the
> decoded info (ie, heap tuples and similar). The test_decoding *tests*
> the decoding API and the external projects use the decoding API as well
> but they don't really decode anything, their role is of filtering and
> deciding the wire protocol mostly.

Yes, I thought test_decoding did decoding and not just use a
backend-internal decoder.

  Bruce Momjian  <br...@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to