Consistent coding for the naming of LR workers

Поиск
Список
Период
Сортировка
От Peter Smith
Тема Consistent coding for the naming of LR workers
Дата
Msg-id CAHut+Pt1xwATviPGjjtJy5L631SGf3qjV9XUCmxLu16cHamfgg@mail.gmail.com
обсуждение исходный текст
Ответы Re: Consistent coding for the naming of LR workers  (Amit Kapila <amit.kapila16@gmail.com>)
Re: Consistent coding for the naming of LR workers  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Re: Consistent coding for the naming of LR workers  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Список pgsql-hackers
Hi,

There are different types of Logical Replication workers -- e.g.
tablesync workers, apply workers, and parallel apply workers.

The logging and errors often name these worker types, but during a
recent code review, I noticed some inconsistency in the way this is
done:
a) there is a common function get_worker_name() to return the name for
the worker type,  -- OR --
b) the worker name is just hardcoded in the message/error

I think it is not ideal to cut/paste the same hardwired strings over
and over. IMO it just introduces an unnecessary risk of subtle naming
differences creeping in.

~~

It is better to have a *single* point where these worker names are
defined, so then all output uses identical LR worker nomenclature.

PSA a small patch to modify the code accordingly. This is not intended
to be a functional change - just a code cleanup.

Thoughts?

------
Kind Regards,
Peter Smith.
Fujitsu Australia

Вложения

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

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Re: Bypassing shared_buffers
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Bypassing shared_buffers