On Wed, Dec 30, 2009 at 1:14 PM, Guillaume Lelarge
>> The application_name should be set as a connection string parameter,
>> not an explicit SET command.
> That was the first thing I wanted to do. But people won't be able to use
> pgAdmin with older PostgreSQL releases if we use the connection string
Yes they will. We changed libpq to ensure that works properly.
>> This ensures that the application name is
>> included in the initial connection log message, and avoids a round
>> trip with the SET query. PQconninfoParse can be used to test if libpq
>> supports application_name at runtime.
> I don't understand that. libpq and the server are two different things.
> You can have a new libpq on your client and an old server. client's
> PQconninfoParse will tell you application_name is available, but it
> could be that the server doesn't understand it. Perhaps I need to get a
> better look at PQconninfoParse, but don't have the time right now.
You need an 8.5 libpq to use application_name in the connection
string. It doesn't matter what server you have, as libpq will ignore
the parameter for older servers. To ensure you have a suitable libpq,
prepare the connection string, and feed it to PQconninfoParse. If you
get a null response, there's a problem (e.g. application_name is not
supported). If you get a non-null response, the connection string is
>> I suspect the patch is also missing some changes to the debugger.
> Probably, I'll look at this.
EnterpriseDB UK: http://www.enterprisedb.com
In response to
pgadmin-hackers by date
|Next:||From: pgAdmin Trac||Date: 2010-01-02 14:37:12|
|Subject: [pgAdmin III] #122: storenode function takes only two parameters
with Slony 2.0|
|Previous:||From: Mark Reid||Date: 2009-12-30 16:15:21|
|Subject: Support for Updatable Views - Edit Grid|