Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: [HACKERS] Why does logical replication launcher set application_name?
Date
Msg-id 12850.1492533455@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Why does logical replication launcher setapplication_name?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Why does logical replication launcher setapplication_name?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Tree view 
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> I think showing bgw_name as backend_type always sounds reasonable.  No
> need to treat external implementations differently.

That's definitely an approach we could use.  It would encourage people
to use short bgw_names, which is a constraint that wasn't especially
apparent before, but I don't think that's a bad thing.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] some review comments on logical rep code
Next
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Interval for launching the table sync worker