Re: Feature Request - DDL deployment with logical replication - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Feature Request - DDL deployment with logical replication
Date
Msg-id 20180331165716.mxe5b6qshqvku7fr@alap3.anarazel.de
Whole thread Raw
In response to Re: Feature Request - DDL deployment with logical replication  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Feature Request - DDL deployment with logical replication  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On 2018-03-31 22:13:42 +0800, Craig Ringer wrote:
> We'll still need a mechanism to transport them to downstreams (like WAL
> messages) and to send responses upstream. For responses I think we will
> finally want to add a backchannel to the logical replication protocol as
> I've wanted for a long while: downstream can send a COPY message on COPY
> BOTH proto back to upstream, which passes it to a callback on the output
> plugin for the output plugin to act on.

Not necessarily?  You can just send out the prepare, wait for all
clients to ack it, and then commit/rollback prepared.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Next
From: Peter Eisentraut
Date:
Subject: Re: Foreign keys and partitioned tables