Re: WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink - Mailing list pgsql-hackers

From Robert Haas
Subject Re: WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink
Date
Msg-id CA+TgmoZZwn0ShJ7RkxnWqVoDPecdDu8h-w_8=8=DHWAg2rTZmg@mail.gmail.com
Whole thread Raw
In response to WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink  (Amit kapila <amit.kapila@huawei.com>)
Responses Re: WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink
Re: WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink
List pgsql-hackers
On Mon, Jun 11, 2012 at 5:30 AM, Amit Kapila <amit.kapila@huawei.com> wrote:
> As per the previous discussion in link below, it seems that fallback
> application name needs to be provided for only
>
> pgbench and oid2name.
>
> http://archives.postgresql.org/message-id/w2g9837222c1004070216u3bc46b3ahbddfdffdbfb46212@mail.gmail.com
>
>
>
> However the title of Todo Item suggests it needs to be done for dblink as
> well.
>
> Please suggest if it needs to be done for dblink, if yes then what should be
> fallback_application_name for it?

Why not 'dblink'?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Mark JSON error detail messages for translation.
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Mark JSON error detail messages for translation.