RE: logical_replication_mode - Mailing list pgsql-hackers

From Zhijie Hou (Fujitsu)
Subject RE: logical_replication_mode
Date
Msg-id OS0PR01MB571605D1816E954C80BAA1DE94E7A@OS0PR01MB5716.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: logical_replication_mode  (Peter Smith <smithpb2250@gmail.com>)
List pgsql-hackers
On Tuesday, August 29, 2023 3:26 PM Peter Smith <smithpb2250@gmail.com> wrote:

Thanks for reviewing.

> 2. DebugLogicalRepStreamingMode
> 
> -/* possible values for logical_replication_mode */
> +/* possible values for debug_logical_replication_streaming */
>  typedef enum
>  {
> - LOGICAL_REP_MODE_BUFFERED,
> - LOGICAL_REP_MODE_IMMEDIATE
> -} LogicalRepMode;
> + DEBUG_LOGICAL_REP_STREAMING_BUFFERED,
> + DEBUG_LOGICAL_REP_STREAMING_IMMEDIATE
> +} DebugLogicalRepStreamingMode;
> 
> Shouldn't this typedef name be included in the typedef.list file?

I think it's unnecessary to add this as there currently is no reference to the name.
See other similar examples like DebugParallelMode, RecoveryPrefetchValue ...
And the name is also not included in BF[1]

[1] https://buildfarm.postgresql.org/cgi-bin/typedefs.pl?branch=HEAD

Best Regards,
Hou zj

pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: Support prepared statement invalidation when result types change
Next
From: Junwang Zhao
Date:
Subject: Re: [PATCH v1] PQputCopyEnd never returns 0, fix the inaccurate comment