Re: Avoid resetting subscription two_phase state to pending when already enabled

From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Zhijie Hou <houzhijie22(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, shveta malik <shvetamalik(at)gmail(dot)com>
Subject: Re: Avoid resetting subscription two_phase state to pending when already enabled
Date: 2026-11-04 13:24:18
Message-ID: ausyAuSbEhJVgfu5@bdtpg
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Wed, Nov 04, 2026 at 03:31:19PM +0530, Amit Kapila wrote:
> But I feel we should add that
> change in behavior for new slot's in the commit message.

+1. I think this behavior change should also be mentioned in the release notes
for the affected branches. Is that also the intention behind adding it to the
commit message?

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhijie Hou 2026-11-04 13:29:44 Re: Avoid using raw xmin of frozen tuples in logicalrep conflict detection
Previous Message Osama Abdul Qader 2026-11-04 13:16:56 Re: Avoid using raw xmin of frozen tuples in logicalrep conflict detection