bgw_type (was Re: [HACKERS] Why does logical replication launcher setapplication_name?)

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема bgw_type (was Re: [HACKERS] Why does logical replication launcher setapplication_name?)
Дата
Msg-id 452d87d8-22f1-f331-480e-420087058700@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Why does logical replication launcher setapplication_name?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: bgw_type (was Re: [HACKERS] Why does logical replication launcherset application_name?)  (Michael Paquier <michael.paquier@gmail.com>)
Re: bgw_type (was Re: [HACKERS] Why does logical replication launcher set application_name?)  (Daniel Gustafsson <daniel@yesql.se>)
Список 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.

Updated patch incorporating the feedback.  I have kept bgw_name as it
was and just added bgw_type completely independently.

One open question is how to treat a missing (empty) bgw_type.  I
currently fill in bgw_name as a fallback.  We could also treat it as an
error or a warning as a transition measure.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Вложения

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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] expanding inheritance in partition bound order
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] expanding inheritance in partition bound order