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

Re: Libpq PGRES_COPY_BOTH - version compatibility

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Libpq PGRES_COPY_BOTH - version compatibility
Date: 2011-03-27 03:09:51
Message-ID: AANLkTi=ubLirJrEdwCs4Y0Za6BbzbmrNeDLNyewo0dLe@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Jan 3, 2011 at 6:55 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> ISTM that the correct fix is to increment to protocol version number to
>> 3.1 and send PGRES_COPY_OUT if the client requests version 3.0.  That's
>> what the version numbers are for, no?
>
> In a way - yes. I assume we didn't do that because it's considered "internal".
>
> It still won't help in my situation though - I need to know what
> version of the libpq headers I have in order to even be able to
> *compile* the program. At runtime, I could check against the server
> version, and get around it.

This is listed on the open items list as "raise protocol version
number", but the above discussion suggests both that this might be
unnecessary and that it might not solve Magnus's problem anyway.

What do we want to do here?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-03-27 04:10:04
Subject: Re: DO hint update?
Previous:From: Robert HaasDate: 2011-03-27 03:01:54
Subject: Re: Performance bug in DO blocks

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