Re: Stopping logical replication protocol - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Stopping logical replication protocol
Date
Msg-id CAMsr+YGy_JM+xJwHVg_KxH82Yk-qVqxy_UgPZn=c4BY7bfE0Mg@mail.gmail.com
Whole thread Raw
In response to Re: Stopping logical replication protocol  (Vladimir Gordiychuk <folyga@gmail.com>)
Responses Re: Stopping logical replication protocol  (Haribabu Kommi <kommi.haribabu@gmail.com>)
List pgsql-hackers
On 21 October 2016 at 19:38, Vladimir Gordiychuk <folyga@gmail.com> wrote:
> Craig, Andres what do you thinks about previous message?

I haven't had a chance to look further to be honest.

Since a downstream disconnect works, though it's ugly, it's not
something I can justify spending a lot of time on, and I already did
spend a lot on it in patch review/updating/testing etc.

I don't know what Andres wants, but I think CopyFail with
ERRCODE_QUERY_CANCELED is fine.

As for plugins that collect changes in memory and only send them on
commit, I'd call them "broken". Not an interesting case IMO. Don't do
that.

-- Craig Ringer                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: Logical Replication WIP
Next
From: Robert Haas
Date:
Subject: Re: Patch: Implement failover on libpq connect level.