From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Application name patch - v3 |
Date: | 2009-12-28 09:07:16 |
Message-ID: | 937d27e10912280107s166263d9habd0b045c43e251a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Dec 27, 2009 at 11:15 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Le 13/11/2009 12:11, Dave Page a écrit :
>> [...]
>>> What about pg_dump/psql setting fallback_application_name?
>>
>> Per Tom, I'm waiting on the possible new array-based libpq connect API
>> which will make a conversion of those utilities from PQsetdbLogin a
>> lot cleaner than moving to PQconnectdb (and all the ugly connection
>> string building that would require).
>>
>
> Is it still to be done? I don't see psql pr pg_dump set an application
> name on alpha 3. There are also pg_restore, vacuumdb, reindexdb, etc.
Yes, still waiting on the new API.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-12-28 09:56:42 | Re: Small locking bugs in hs |
Previous Message | Robert Haas | 2009-12-28 08:22:14 | Re: [PATCH] bugfix for int2vectorin |