Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Why does logical replication launcher setapplication_name? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Why does logical replication launcher setapplication_name?
Date
Msg-id 576b0a5e-15b5-38b6-00bc-9ec71e524ffe@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Why does logical replication launcher set application_name?  (Noah Misch <noah@leadboat.com>)
Responses Re: [HACKERS] Why does logical replication launcher set application_name?  (Masahiko Sawada <sawada.mshk@gmail.com>)
Re: [HACKERS] Why does logical replication launcher setapplication_name?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
bgw_type (was Re: [HACKERS] Why does logical replication launcher setapplication_name?)  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Tree view 
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.

-- 
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
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] pg_config --version-num
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] Patch: Add --no-comments to skip COMMENTs with pg_dump