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?

> > Do you mean the WAL logical stream now has timeline information and 3rd
> > party software should know about that?
> It's less about knowing about it, and more about being empowering new 
> usecases.
> But, TBH, in this case I'm not sure what the point would be - given
> there's no way to sanely create and use such slots, I don't think the
> timeline following has advantages on its own, it's imo more of a
> stepping stone.

OK, makes sense.  Let me know if we should add:

> >> I also wonder if ability to run SQL queries on walsender connected to a
> >> database is worth mentioning (replication=database kind of connection).

  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