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

Re: pgAdmin III v1.10.2 released

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, Dale J Thompson <Dale(dot)J(dot)Thompson(at)noaa(dot)gov>, pgAdmin Support List <pgadmin-support(at)postgresql(dot)org>
Subject: Re: pgAdmin III v1.10.2 released
Date: 2010-03-17 16:33:32
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-support
2010/3/17 Guillaume Lelarge <guillaume(at)lelarge(dot)info>:
> Le 17/03/2010 17:01, Devrim GÜNDÜZ a écrit :
>> On Wed, 2010-03-17 at 16:52 +0100, Guillaume Lelarge wrote:
>>> You should because I don't have any idea what you are talking about.
>> I sent build log yesterday:
> Oops, sorry. Didn't think they were related.
> I found this:
> pg_valid_server_encoding_id() is exported by 8.3's libpq, but it does
> not exist in 8.2 and before.  What is evidently happening is that psql
> is binding to an old copy of  Check your PG installation.
> in a Tom Lane's mail on the same kind of issue.
> Our issue comes from revision 8087
> (
> I don't see an easy way to get around this. Either we drop that code, or
> we explicitely state that pgAdmin works only with recent libpq (recent
> meaning here 8.3+). Dave, did I misunderstand something? what's your
> point of view on this issue?

I don't see any reason why we should lose important functionality to
ensure a modern pgAdmin will *build* with an old PostgreSQL. If we
have to do that, it would become very difficult to know how any given
build will behave.

Dave Page
EnterpriseDB UK:
PG East Conference:

In response to


pgadmin-support by date

Next:From: Vinicius BorgesDate: 2010-03-17 16:33:59
Subject: Re: Problem with in pgadmin3-1.10.2
Previous:From: Guillaume LelargeDate: 2010-03-17 16:16:49
Subject: Re: pgAdmin III v1.10.2 released

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