Re: Separate GUC for replication origins

Поиск
Список
Период
Сортировка
От Keisuke Kuroda
Тема Re: Separate GUC for replication origins
Дата
Msg-id CANDwggK+Hb2JgFGVNpp2gf1cf_eL_72tgOZaKx3Wv_P2kWGsPA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Separate GUC for replication origins  (Peter Eisentraut <peter@eisentraut.org>)
Список pgsql-hackers
Hi Euler,

As you may have already read, separating the max_replication_slots parameter
is also discussed in the following thread.


https://www.postgresql.org/message-id/flat/CAA4eK1KF4MbyWmPj9ctNo8Fiei%3DK91RGYtzV5ELeCvR%3D_rqNgg%40mail.gmail.com#3012c5c18e40e
21ac553b42d53249e42

I agree with separating the parameters.
I think we need to discuss the names of the parameter.
Parameter names were also discussed in the above thread.
It was suggested to name them 'max_replication_origin_states' or
'max_tracked_replication_origins'.

Personally, I find 'max_replication_origin_states' easier to understand,
although it is a long name.

Best Regards,
Keisuke Kuroda
NTT Comware



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