On Thu, May 4, 2017 at 05:09:40PM -0700, Andres Freund wrote:
> > > I would not in any way refer to logical decoding as being only a proof
> > > of concept, even before logical replication.
> >
> > The community ships a reliable logical _encoding_, and a test logical
> > _decoding_.
>
> Yes, so what? What you said is "I didn't think logical decoding was
> really more than a proof-of-concept until now", which is plainly wrong,
> given I know a significant number of users using it in production. Some
> of them are well known & large enterprises, and it's used to enable
> critical things.
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:
https://www.postgresql.org/message-id/a6d13cf7-fbf8-913c-2353-f149c6f95fdc%402ndquadrant.com> >> Or the ability of
logicaldecoding to follow timeline switches.> > I didn't think logical decoding was really more than a
proof-of-concept>until now.
Now, if the "encoding" was changed so the external decoders can do more,
or the API we supply to the decoders has new abilities, that is fine to
mention, but someone needs to say that. That is an "encoding" change,
right?
I said nothing about external decoders, only the user-interface decoder
we ship.
I assume it is this commit:
Author: Simon Riggs <simon@2ndQuadrant.com>2017-03-22 [1148e22a8] Teach xlogreader to follow timeline switches Teach
xlogreaderto follow timeline switches Uses page-based mechanism to ensure we’re using the correct timeline. Tests
areincluded to exercise the functionality using a cold disk-level copy of the master that's started up as a replica
withslots intact, but the intended use of the functionality is with later features. Craig Ringer, reviewed by
SimonRiggs and Andres Freund
-- Bruce Momjian <bruce@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 +