Re: WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink

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/w2g9837222c1004070216u3bc46b3ahbdd
fdffdbfb46212(at)mail(dot)gmail(dot)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?

From: pgsql-hackers-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Amit kapila
Sent: Friday, June 08, 2012 10:45 PM
To: pgsql-hackers(at)postgresql(dot)org
Subject: [HACKERS] WIP patch for Todo Item : Provide
fallback_application_name in contrib/pgbench, oid2name, and dblink

This patch is to provide support for fallback application name for
contrib/pgbench, oid2name, and dblink.

Currently I have done the implementation for pgbench. The implementation is
same as in psql.

Before creating a final patch, I wanted to check whether my direction for
creating a patch is what is expected from this Todo item.

I have done the basic testing for following 2 scenario's

1. After implementation, if during run of pgbench, we query pg_stat_activity
it displays the application name as pgbench

2. It displays the application name in log file also.

Suggestions?