| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Daniil Davydov' <3danissimo(at)gmail(dot)com> |
| Cc: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: Wrong comment for ReplicationSlotCreate |
| Date: | 2026-01-05 04:16:35 |
| Message-ID: | TY7PR01MB145544AAAE6914EEE0A0C8B48F586A@TY7PR01MB14554.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Daniil, Chao,
I was the main author of 1462aad2. It is enough to remove outdated comments atop
the definition. In other words, your patch looks good to me.
If needed, we can also notify developers that the two-phase option should not be
altered while decoding WAL records. In logical replication, we ensure that the
subscription is disabled and there are no apply workers. However, I don't think
such comments can be atop the ReplicationSlotCreate(). Maybe around
ReplicationSlotAlter(), but it may be out of scope of the initial motivation.
By the way, the comment may have been broken since a8fd13. Even when the
subscription was defined with two_phase=on, the backend creates the slot with
two_phase = off. The configuration is changed after the tablesync is done.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2026-01-05 04:28:55 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Chengpeng Yan | 2026-01-05 04:15:25 | Re: Add a greedy join search algorithm to handle large join problems |