Re: Libpq PGRES_COPY_BOTH - version compatibility - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Libpq PGRES_COPY_BOTH - version compatibility
Date
Msg-id AANLkTimKhGTXyeJWtMw09sTkRrVobAyAVSYa0=sgXj0g@mail.gmail.com
Whole thread Raw
In response to Re: Libpq PGRES_COPY_BOTH - version compatibility  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Sun, Jan 2, 2011 at 4:36 AM, Magnus Hagander <magnus@hagander.net> wrote:
> On Wed, Dec 29, 2010 at 19:49, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Dec 29, 2010, at 10:14 AM, Magnus Hagander <magnus@hagander.net> wrote:
>>> We can be held responsible for the packaging decisions if they use
>>> *our* "make install" commands, imho.
>>
>> Yep.
>
> So, as I see it there are two ways of doing it - install a
> catversion.h file and include it from libpq-fe.h, or modify the
> libpq-fe.h. I still think modifying libpq-fe.h is the better of these
> choices - but either of them would work. But is the catversion value
> really the best interface for the user? This is about libpq
> functionality level, which really has nothing to do with the backend
> catalog, does it?

It doesn't seem to me that a change of this type requires a catversion bump.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Basic foreign table support.
Next
From: Robert Haas
Date:
Subject: Re: management of large patches