Re: [HACKERS] Why does logical replication launcher setapplication_name?
От | Petr Jelinek |
---|---|
Тема | Re: [HACKERS] Why does logical replication launcher setapplication_name? |
Дата | |
Msg-id | 1383028f-688a-060c-3a57-13d33d52381c@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Why does logical replication launcher setapplication_name? (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] Why does logical replication launcher setapplication_name?
Re: [HACKERS] Why does logical replication launcher set application_name? |
Список | pgsql-hackers |
On 02/06/17 21:05, Peter Eisentraut wrote: > On 6/2/17 02:31, Masahiko Sawada wrote: >> I'd say current patch makes the user difficult to >> distinguish between apply worker and table sync worker. > > We could arguably make apply workers and sync workers have different > bgw_type values. But if you are interested in that level of detail, you > should perhaps look at pg_stat_subscription. pg_stat_activity only > contains the "common" data, and the process-specific data is in other views. > Agreed with this. However, I am not sure about the bgw_name_extra. I think I would have preferred keeping full bgw_name field which would be used where full name is needed and bgw_type where only the worker type is used. The concatenation just doesn't sit well with me, especially if it requires the bgw_name_extra to start with space. -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: