Skip site navigation (1) Skip section navigation (2)

Re: Issue with libpq < 8.4

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Issue with libpq < 8.4
Date: 2010-08-24 11:45:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
On Tue, Aug 24, 2010 at 12:41 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> So can't we do something like:
> if (conninfoparse_shows_we_have_application_name_support)
>   use connstr_with_appname;
> else
>   use connstr_without_appname;
> #else
>   use connstr_without_appname
> #endif
> ? That way it should still work with older libpq, just not set
> application_name...

That would probably work. We should probably have a runtime check for
Windows, as we do for the EDB libpq functions.

When can I expect the patch?

Dave Page
Twitter: @pgsnake

EnterpriseDB UK:
The Enterprise Postgres Company

In response to


pgadmin-hackers by date

Next:From: Magnus HaganderDate: 2010-08-24 11:48:53
Subject: Re: Issue with libpq < 8.4
Previous:From: Magnus HaganderDate: 2010-08-24 11:41:35
Subject: Re: Issue with libpq < 8.4

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group