From: | vignesh C <vignesh21(at)gmail(dot)com> |
---|---|
To: | Shubham Khanna <khannashubham1197(at)gmail(dot)com> |
Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Adding a '--two-phase' option to 'pg_createsubscriber' utility. |
Date: | 2024-12-11 08:38:23 |
Message-ID: | CALDaNm06xr_7ynykwnKNuRY0zTRFkVUGndsO7OU1437=M07XwQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 11 Dec 2024 at 11:21, Shubham Khanna
<khannashubham1197(at)gmail(dot)com> wrote:
>
> On Wed, Dec 11, 2024 at 4:21 AM Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
> I have fixed the given comments. The attached patch contains the
> suggested changes.
Since all the subscriptions are created based on the two_phase option
provided, there is no need to store this for each database:
@@ -53,6 +54,7 @@ struct LogicalRepInfo
char *pubname; /* publication name */
char *subname; /* subscription name */
char *replslotname; /* replication slot name */
+ bool two_phase; /* two-phase enabled
for the subscription */
dbinfo[i].dbname = cell->val;
+ dbinfo[i].two_phase = opt->two_phase;
if (num_pubs > 0)
How about we handle something like in the attached changes.
Regards,
Vignesh
Attachment | Content-Type | Size |
---|---|---|
Remove_dbwise_two_phase.patch | text/x-patch | 4.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | RECHTÉ Marc | 2024-12-11 08:59:55 | Re: Logical replication timeout |
Previous Message | Andrei Lepikhov | 2024-12-11 08:35:43 | Add Postgres module info |