Re: Wrong comment for ReplicationSlotCreate

From: Daniil Davydov <3danissimo(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Wrong comment for ReplicationSlotCreate
Date: 2025-12-30 10:07:22
Message-ID: CAJDiXghEf_BviOC9Ci-it2p1v0DOa+0yqfCyBV89rXSkcd-5JA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Tue, Dec 30, 2025 at 4:18 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>
> But I think the updated version is too simple. It loses the information that enabling two_phase later can result in missing PREPARE.
>
> So, I would suggest something like:
> ```
> * two_phase: If enabled, allows decoding of prepared transactions.
> * Note that enabling this option after decoding has already advanced
> * may result in missing PREPARE records for transactions that were
> * prepared before the option was enabled.
>
> ```

Thanks for the review!

As far as I understand, if the publisher prepares a transaction and
then subscriber
tries to create a subscription, walsender will wait until the prepared
transaction is
finished (during execution of CREATE_REPLICATION_SLOT command).
We can find this logic inside the SnapBuildFindSnapshot function. Thus, we
cannot miss any PREPARE record for the created slot.

Am I missing something?

--
Best regards,
Daniil Davydov

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Yugo Nagata 2025-12-30 10:01:45 Fix comments on _bt_skiparray_strat_increment/decrement