Re: Force streaming every change in logical decoding
Masahiko Sawada <sawada.mshk@gmail.com>
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, "shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>,
Peter Smith <smithpb2250@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-12-22T07:59:30Z
Lists: pgsql-hackers
On Thu, Dec 22, 2022 at 4:18 PM Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote: > > Dear Amit, > > Thank you for updating the patch. I have also checked the patch > and basically it has worked well. Almost all things I found were modified > by v4. > > One comment: while setting logical_decoding_mode to wrong value, > I got unfriendly ERROR message. > > ``` > postgres=# SET logical_decoding_mode = 1; > ERROR: invalid value for parameter "logical_decoding_mode": "1" > HINT: Available values: , immediate > ``` > > Here all acceptable enum should be output as HINT, but we could not see the empty string. > Should we modify config_enum_get_options() for treating empty string, maybe > like (empty)? Good point. I think the hint message can say "The only allowed value is \"immediate\" as recovery_target does. Or considering the name of logical_decoding_mode, we might want to have a non-empty string, say 'normal' as Kuroda-san proposed, as the default value. Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com
Commits
-
Add 'logical_decoding_mode' GUC.
- 5de94a041ed7 16.0 landed
-
Clean up some inconsistencies with GUC declarations
- d9d873bac670 16.0 cited