Re: Decoding of two-phase xacts missing from CREATE_REPLICATION_SLOT command - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Decoding of two-phase xacts missing from CREATE_REPLICATION_SLOT command
Date
Msg-id 153dc41cb01c62b6814a9a6d57bd6387ef1e89f7.camel@j-davis.com
Whole thread Raw
In response to Re: Decoding of two-phase xacts missing from CREATE_REPLICATION_SLOT command  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Decoding of two-phase xacts missing from CREATE_REPLICATION_SLOT command
List pgsql-hackers
On Wed, 2021-06-09 at 17:27 +0530, Amit Kapila wrote:
> 2. In the main patch [1], we do send two_phase option even during
> START_REPLICATION for the very first time when the two_phase can be
> enabled. There are reasons as described in the worker.c why we can't
> enable it during CREATE_REPLICATION_SLOT. 

I'll have to catch up on the thread to digest that reasoning and how it
applies to decoding vs. replication. But there don't seem to be changes
to START_REPLICATION for twophase, so I don't quite follow your point.

Are you saying that we should not be able to create slots with twophase
at all until the rest of the changes go in?

> Now, if we want to do
> protocol changes, I wonder why only do some changes and leave the
> rest
> for the next version?

I started this thread because it's possible to create a slot a certain
way using the SQL function create_logical_replication_slot(), but it's
impossible over the replication protocol. That seems inconsistent to
me.

Regards,
    Jeff Davis





pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Decoding of two-phase xacts missing from CREATE_REPLICATION_SLOT command
Next
From: Thomas Munro
Date:
Subject: BF assertion failure on mandrill in walsender, v13