Re: Issue with libpq < 8.4 - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Issue with libpq < 8.4
Date
Msg-id AANLkTi=_xiib0fhHdQ9RqhWvQUXii4-w=+H883iObMh8@mail.gmail.com
Whole thread Raw
In response to Re: Issue with libpq < 8.4  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: Issue with libpq < 8.4  (Magnus Hagander <magnus@hagander.net>)
List pgadmin-hackers
On Tue, Aug 24, 2010 at 12:20 PM, Guillaume Lelarge
<guillaume@lelarge.info> wrote:
>
> Can't we just have it set a variable we could check with a #ifdef? We
> don't use PQconninfoParse in many files (actually, two). So it would be
> pretty easy to add the #ifdef line, so that it won't be a big issue for
> packagers.

We use PQconninfoParse to check to ensure we have a new enough libpq
to use application_name, so we can avoid sending it with older libpqs.
If we disable the check for older libpqs, then we'll always get an
error with them. The only way to fix that would be to only allow a 9.0
libpq to be used.

The current code at least allows 8.4 and 9.0 libpqs.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company

pgadmin-hackers by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: Issue with libpq < 8.4
Next
From: Magnus Hagander
Date:
Subject: Re: Issue with libpq < 8.4