RE: Rework LogicalOutputPluginWriterUpdateProgress

Поиск
Список
Период
Сортировка
От wangw.fnst@fujitsu.com
Тема RE: Rework LogicalOutputPluginWriterUpdateProgress
Дата
Msg-id OS3PR01MB6275482D88E78CC90D77D38B9EB69@OS3PR01MB6275.jpnprd01.prod.outlook.com
обсуждение исходный текст
Ответ на Re: Rework LogicalOutputPluginWriterUpdateProgress  (Peter Smith <smithpb2250@gmail.com>)
Ответы RE: Rework LogicalOutputPluginWriterUpdateProgress  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
Список pgsql-hackers
On Fri, Mar 3, 2023 8:18 AM Peter Smith <smithpb2250@gmail.com> wrote:
> 

Thanks for your comments.

> 1.
> +
> +static void UpdateProgressAndKeepalive(LogicalDecodingContext *ctx,
> +    bool finished_xact);
> +
> +static bool is_keepalive_threshold_exceeded(LogicalDecodingContext *ctx);
> 
> 1a.
> There is an unnecessary extra blank line above the UpdateProgressAndKeepalive.

Removed.

> ~
> 
> 1b.
> I did not recognize a reason for the different naming conventions.
> Here are two new functions but one is CamelCase and one is snake_case.
> What are the rules to decide the naming?

I used the snake_case style for the function UpdateProgressAndKeepalive in the
previous version, but it was confusing because it shared the same parameter name
with the functions StartupDecodingContext, CreateInitDecodingContext and
CreateDecodingContext. To avoid this confusion, and since both naming styles
exist in this file, I changed it to CamelCase style.

Attach the new patch.

Regards,
Wang wei

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: "wangw.fnst@fujitsu.com"
Дата:
Сообщение: RE: Support logical replication of DDLs
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Deduplicate logicalrep_read_tuple()