| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "shiy(dot)fnst(at)fujitsu(dot)com" <shiy(dot)fnst(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Force streaming every change in logical decoding |
| Date: | 2022-12-10 05:48:14 |
| Message-ID: | CAFiTN-snBe19pbV=VrrqO7W_v=O0B7R0Ajv0vjnXr+kBygrsKA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 7, 2022 at 5:16 AM Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
+1 for the idea
>
> There is potential for lots of developer GUCs for testing/debugging in
> the area of logical replication but IMO it might be better to keep
> them all separated. Putting everything into a single
> 'logical_replication_mode' might cause difficulties later when/if you
> want combinations of the different modes.
>
> For example, instead of
>
> logical_replication_mode = XXX/YYY/ZZZ
>
> maybe something like below will give more flexibility.
>
> logical_replication_dev_XXX = true/false
> logical_replication_dev_YYY = true/false
> logical_replication_dev_ZZZ = true/false
>
Even I agree that usability wise keeping them independent is better.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2022-12-10 06:03:06 | Re: Force streaming every change in logical decoding |
| Previous Message | Michael Paquier | 2022-12-10 04:07:29 | Re: Generate pg_stat_get_* functions with Macros |