| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | bgw_type (was Re: Why does logical replication launcher set application_name?) |
| Date: | 2017-08-31 19:49:19 |
| Message-ID: | 452d87d8-22f1-f331-480e-420087058700@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Add-background-worker-type.patch | text/plain | 13.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-08-31 19:51:20 | Re: expanding inheritance in partition bound order |
| Previous Message | Robert Haas | 2017-08-31 19:38:33 | Re: expanding inheritance in partition bound order |