| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why does logical replication launcher set application_name? |
| Date: | 2017-06-02 19:08:09 |
| Message-ID: | 2abb2ae9-2b09-7ee0-9789-493686710e9e@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.
>
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-06-02 19:24:48 | Re: Error while creating subscription when server is running in single user mode |
| Previous Message | Peter Eisentraut | 2017-06-02 19:05:33 | Re: Why does logical replication launcher set application_name? |