From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Question and suggestion about application binary compatibility policy |
Date: | 2016-06-01 13:44:54 |
Message-ID: | 1464788694.21529.27.camel@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> However, the problem I pointed out is that when the new library is
> incompatible with the older one, say the major version of libpq.dll
> changes from 5 to 6, the application user and/or developer cannot
> notice the incompatibility immediately and easily. On Unix/Linux,
> the application fails to start because the older library is not
> found. On the other hand, the application will start on Windows and
> probably cause difficult trouble due to the incompatibility.
I don't think this is a very good situation, but I have no idea if this
can be solved. However, I'd prefer a technical solution over a
documentation one.
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 | Tom Lane | 2016-06-01 14:10:45 | Re: Rename max_parallel_degree? |
Previous Message | Thom Brown | 2016-06-01 13:37:14 | Re: array of domain types |