From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
---|---|
To: | 'Shlok Kyal' <shlok(dot)kyal(dot)oss(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Shubham Khanna <khannashubham1197(at)gmail(dot)com> |
Subject: | RE: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility. |
Date: | 2025-02-05 02:19:39 |
Message-ID: | OSCPR01MB1496689B1F157DAD598F9E035F5F72@OSCPR01MB14966.jpnprd01.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear Shlok,
> 4. Instead of warning we should throw an error here:
> + if (PQresultStatus(res) != PGRES_TUPLES_OK)
> + {
> + pg_log_warning("could not obtain publication information: %s",
> + PQresultErrorMessage(res));
> +
I don't think so. ERROR evokes user to retry the command or recreate the physical
replica, but the conversion has already been finished when drop_all_publications()
is called. Cleanup operations should not affect the final result.
drop_primary_replication_slot() and drop_failover_replication_slots() raise WARNING
when they fail to drop objects because they are just cleanup functions.
I feel we can follow this manner.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira | 2025-02-05 02:46:12 | Re: Separate GUC for replication origins |
Previous Message | Vladlen Popolitov | 2025-02-05 02:19:27 | Re: Make COPY format extendable: Extract COPY TO format implementations |