Re: Decoding of two-phase xacts missing from CREATE_REPLICATION_SLOT command

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Ajin Cherian <itsajin(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <akapila(at)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>
Subject: Re: Decoding of two-phase xacts missing from CREATE_REPLICATION_SLOT command
Date: 2021-06-09 22:43:14
Message-ID: 153dc41cb01c62b6814a9a6d57bd6387ef1e89f7.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2021-06-09 22:47:20 BF assertion failure on mandrill in walsender, v13
Previous Message Jeff Davis 2021-06-09 22:12:57 Re: Decoding of two-phase xacts missing from CREATE_REPLICATION_SLOT command