I have created the patch by including fallback_application_name for dblink as well. In this I have used the name of fallback_application_name as dblink.
Please let me know your suggestions regarding the same. -----Original Message----- From: Robert Haas [mailto:robertmh...@gmail.com] Sent: Wednesday, June 13, 2012 12:13 AM To: Amit Kapila Cc: pgsql-hackers@postgresql.org Subject: Re: [HACKERS] WIP patch for Todo Item : Provide fallback_application_name in contrib/pgbench, oid2name, and dblink On Mon, Jun 11, 2012 at 5:30 AM, Amit Kapila <amit.kap...@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/w2g9837222c1004070216u3bc46b3ahbdd fdffdbfb46...@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
fallback_application_name.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
