On Tue, Apr 25, 2017 at 07:17:20PM -0700, Andres Freund wrote:
> On 2017-04-25 22:13:00 -0400, Bruce Momjian wrote:
> > On Tue, Apr 25, 2017 at 06:40:08PM -0700, Andres Freund wrote:
> > > On 2017-04-25 21:19:41 -0400, Bruce Momjian wrote:
> > > > On Tue, Apr 25, 2017 at 06:51:47AM +0200, Petr Jelinek wrote:
> > > > > Or the ability of logical decoding to follow timeline switches.
> > > >
> > > > When you say "logical decoding", you don't mean contrib/test_decoding?
> > >
> > > No. test_decoding is just an example output plugin ("formatting" the
> > > changes), but there's in-production users of logical decoding out
> > > there. So features adding to logical decoding in general, are worth to
> > > be mention in general.
> >
> > Yes, but I am still trying to find out what changed because we don't
> > ship much that does "decoding" except contrib/test_decoding. Are you
> > saying logical information is included in WAL?
>
> We ship an extension API [1] [2] that allows to use decoding. And that
> the internals of that API now knows how to deal with timeline changes.
> You could e.g. compare it with the FDW API now providing the ability to
> do aggregate pushdown or such.
Yes, if we changed the developer-visible API we should mention that in
the release notes.
> > > >> I also wonder if ability to run SQL queries on walsender connected to a
> > > >> database is worth mentioning (replication=database kind of connection).
>
> Yes, but we're still discussing the feature's exact look nearby.
OK, please keep us up-to-date on what needs to be added.
-- 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 +
