From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Issue with libpq < 8.4 |
Date: | 2010-08-24 13:25:43 |
Message-ID: | AANLkTik-YDEXJHrXMAXvNOQh_COdg8+XOu2viHaj4Rmj@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Tue, Aug 24, 2010 at 2:23 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Le 24/08/2010 14:05, Magnus Hagander a écrit :
>> On Tue, Aug 24, 2010 at 2:01 PM, Guillaume Lelarge
>> <guillaume(at)lelarge(dot)info> wrote:
>>> Le 24/08/2010 13:51, Dave Page a écrit :
>>>> On Tue, Aug 24, 2010 at 12:48 PM, Magnus Hagander <magnus(at)hagander(dot)net>
>>>> wrote:
>>>>> Actually, what happens if we try to use PQconnect() with
>>>>> applicaiton_name on an older version? I assume it fails, and not just
>>>>> works and ignores it?
>>>>
>>>> iirc, yes.
>>>>
>>>
>>> We have this in the log:
>>>
>>> FATAL: unrecognized configuration parameter "application_name"
>>>
>>> And then it connects.
>>>
>>> At least with a 9.0 libpq and a 8.3.0 PostgreSQL server.
>>
>> Yeah, the interesting thing would be an 8.3 libpq, if you just throw
>> it the connection string and don't try to use PQparseconnInfo().
>>
>
> It fails. If the user has a 8.3 libpq, we should not send the
> application_name connection parameter.
That means Dave is perfectly correct, and thus someone needs to write
that patch ;)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2010-08-24 20:33:58 | Re: GSoC database modeler [Luis Ochoa] |
Previous Message | Guillaume Lelarge | 2010-08-24 12:23:43 | Re: Issue with libpq < 8.4 |