From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 10 release notes |
Date: | 2017-04-25 19:29:01 |
Message-ID: | 20170425192901.GZ7513@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 25, 2017 at 08:12:05PM +0200, Petr Jelinek wrote:
> On 25/04/17 17:01, Bruce Momjian wrote:
> >
> >> I also wonder if ability to run SQL queries on walsender connected to a
> >> database is worth mentioning (replication=database kind of connection).
> >
> > Uh, why would that be important to users?
>
> Because every tool that uses logical decoding to capture changes does not
> need to open extra connection to fetch initial state.
>
> (and we document much less user visible changes than this in the release
> notes)
Are you saying that 3rd party applications that use logical WAL records
need to know about that? Can you provide some text?
> >> Or the ability of logical decoding to follow timeline switches.
> >
> > I didn't think logical decoding was really more than a proof-of-concept
> > until now.
> >
>
> Huh?
Uh, the only logical decoding code that I know we ship pre-PG 10 is
contrib/test_decoding/.
--
Bruce Momjian <bruce(at)momjian(dot)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 +
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-04-25 19:29:15 | Re: Interval for launching the table sync worker |
Previous Message | Peter Eisentraut | 2017-04-25 19:26:06 | Re: Re: logical replication and PANIC during shutdown checkpoint in publisher |