From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Question and suggestion about application binary compatibility policy |
Date: | 2016-05-30 07:51:07 |
Message-ID: | 1464594667.2179.48.camel@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
> - Build an embedded SQL C application with PostgreSQL 9.2.
> - Distribute the app without ecpg nor libpq libraries. Require users
> to install PostgreSQL client which includes ecpg and libpq libraries.
> - Use the app with newer PostgreSQL major versions without rebuilding
> the app. That is, the users just replaces the PostgreSQL client.
>
> I expect this is legal, because the so_major versions of ecpg and
> libpq are 6 and 5 respectively for all PostgreSQL 9.x versions so
> far. However, I could not find any description of this binary
> compatibility policy in the manual, so I haven't been able to answer
> the customer.
Sorry I fail to understand what you mean with "legal"? Are you
wondering about license restrictions? There are none.
As for compatibility, that's what major version numbers are for. This
is not a PostgreSQL topic, but a general system one as for instance the
same holds for libc.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2016-05-30 08:01:27 | Re: Question and suggestion about application binary compatibility policy |
Previous Message | Tom Dunstan | 2016-05-30 04:37:56 | IPv6 link-local addresses and init data type |