Re: [HACKERS] Why does logical replication launcher setapplication_name?
От | Peter Eisentraut |
---|---|
Тема | Re: [HACKERS] Why does logical replication launcher setapplication_name? |
Дата | |
Msg-id | 2abb2ae9-2b09-7ee0-9789-493686710e9e@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?
|
Список | pgsql-hackers |
On 5/30/17 23:10, Peter Eisentraut wrote: > Here is a proposed solution that splits bgw_name into bgw_type and > bgw_name_extra. bgw_type shows up in pg_stat_activity.backend_type. > Uses of application_name are removed, because they are no longer > necessary to identity the process type. > > This code appears to be buggy because I sometimes get NULL results of > the backend_type lookup, implying that it couldn't find the background > worker slot. This needs another look. I would like some more input on this proposal, especially from those have have engineered the extended pg_stat_activity content. If we don't come to a quick conclusion on this, I'd be content to leave PG10 as is and put this patch into the next commit fest. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: