Postgres Pro
Downloads
Home   >   mailing lists

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

From Craig Ringer
Subject Re: [HACKERS] Why does logical replication launcher set application_name?
Date
Msg-id CAMsr+YGWZMwRXdvcJ+rLuQe0kHi37=9MRgs3PppExq_FpratPQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Why does logical replication launcher set application_name?  (Kuntal Ghosh <kuntalghosh.2007@gmail.com>)
Responses Re: [HACKERS] Why does logical replication launcher set application_name?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On 12 April 2017 at 13:34, Kuntal Ghosh <kuntalghosh.2007@gmail.com> wrote:

> For backend_type=background worker, application_name shows the name of
> the background worker (BackgroundWorker->bgw_name). I think we need
> some way to distinguish among different background workers. But,
> application_name may not be the correct field to show the information.

It's better than (ab)using 'query' IMO.

I'd rather an abbreviated entry to address Tom's concerns about
format. 'lrlaunch' or whatever.

-- Craig Ringer                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] TAP tests take a long time
Next
From: Noah Misch
Date:
Subject: Re: [HACKERS] Add pgstathashindex() to get hash index table statistics.